Nawabshah Jn. to Hyderabad Jn
Shalimar Express 28DN — within 15 minutes of the scheduled time 44% of the time, typically 22 minutes late, over 10 days of recorded runs across every stop of its full journey, not this segment alone. That is its whole-journey record, a different promise from this leg alone: over just Nawabshah Jn. to Hyderabad Jn it typically makes up 7 min, from 22 recorded runs. At Hyderabad Jn it has typically arrived 40 minutes late, from 34 recorded runs.
Every train, compared
13 of 13 with 7+ daysOver this leg is the CHANGE in a train's delay between Nawabshah Jn. and Hyderabad Jn on the same run — not how late it arrives; a train can run late through its whole journey and still show no change here. — means either too few recorded runs on this leg, or — permanently, for a train whose journey starts right here at Nawabshah Jn. — no booked arrival at Nawabshah Jn. to measure from at all. Figures cover runs recorded between 30 July 2026 and 4 October 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 2Khyber Mail 2DN | 00:10 +2d | 02:00 +2d | 1h 50m | 116 km | +2h 02m | 7% | adds 8 min · 21 |
| 146Sukkur Express 146DN | 00:55 +1d | 04:05 +1d | 3h 10m | not measured yet | +19 min | 39% | makes up 42 min · 36 |
| 38Fareed Express 38DN | 02:04 +1d | 04:25 +1d | 2h 21m | not measured yet | +44 min | 14% | makes up 12 min · 30 |
| 26Bahauddin Zikria Express 26DN | 02:56 +1d | 05:10 +1d | 2h 14m | 115 km | +1h 10m | 10% | makes up 6 min · 23 |
| 10Allama Iqbal Express 10DN | 03:50 +1d | 06:00 +1d | 2h 10m | 115 km | +53 min | 24% | makes up 2 min · 35 |
| 8Tezgam 8DN | 04:56 +1d | 07:10 +1d | 2h 14m | 115 km | +58 min | 17% | no change · 37 |
| 34Pak Business 34DN | 06:12 +1d | 08:15 +1d | 2h 03m | 116 km | +1h 05m | 18% | adds 2 min · 37 |
| 18Millat Express 18DN | 07:23 +1d | 09:30 +1d | 2h 07m | 115 km | +2h 37m | 10% | makes up 1 min · 38 |
| 16Karachi Express 16DN | 08:12 +1d | 10:15 +1d | 2h 03m | 116 km | +2h 05m | 13% | makes up 4 min · 38 |
| 48Rehman Baba Express 48DN | 11:25 +1d | 13:45 +1d | 2h 20m | 115 km | +2h 20m | 13% | makes up 12 min · 35 |
| 14Awam Express 14DN | 13:18 +1d | 15:55 +1d | 2h 37m | 116 km | +2h 09m | 8% | makes up 20 min · 38 |
| 12Hazara Express 12DN | 18:47 +1d | 21:05 +1d | 2h 18m | 115 km | +1h 17m | 10% | makes up 6 min · 36 |
| 28Shalimar Express 28DN | 22:10 | 00:05 +1d | 1h 55m | not measured yet | +22 min | 44% | makes up 7 min · 22 |
What the marks mean
- Departs · Arrives — scheduled local times, published Pakistan Railways timetable
- +1d — a stop on a later day of the train's own run, not a date
- Typical delay · On-time — the train's whole journey, not this segment alone; typical is the median of its recorded stop arrivals, and on-time is within 15 minutes of the scheduled time
- — — fewer than 7 days of recorded runs for that train
- Over this leg — the change in each train's delay between the two stations above, counted on runs recorded at both (a run whose two stations were logged a day apart is matched too, when that day-shifted leg length matches the train's usual one). “adds” means the train picked up extra delay over this stretch; “makes up” means it arrived less late than it left; “no change” means neither. The figure shown is the middle (median) run: no more than half of a train's counted runs did WORSE than it, and no more than half did better — never a claim that exactly half did either, which isn't always possible to state.
- A large “makes up” usually says more about the leg than the train: where several services on this page all recover time, the stretch is booked with room in it. It never means the train ran early — only that it was less late arriving than departing.
- — — in that column: fewer than 7 runs recorded at both stations on the leg's usual booked times, or — permanently, for a train whose journey starts at this page's origin station — no booked arrival there to measure from at all, which will not fill in with more archive age.
Every service in detail
Typical delay and on-time share are the train's whole journey, from 7+ days of recorded runs. Over this leg is the change in that train's delay between the two stations, from runs recorded at both.
- Khyber Mail 2DN2خیبر میل 2 ڈائون00:10 +2d→02:00 +2d1h 50m7% on time · +2h 02madds 8 min over this leg · 21 runs
- Sukkur Express 146DN146سکھر ایکسپریس146ڈاؤن00:55 +1d→04:05 +1d3h 10m39% on time · +19 minmakes up 42 min over this leg · 36 runs
- Fareed Express 38DN38فرید ایکسپریس 38 ڈائون02:04 +1d→04:25 +1d2h 21m14% on time · +44 minmakes up 12 min over this leg · 30 runs
- Bahauddin Zikria Express 26DN26بہائو الدین زکریا ایکسپریس26 ڈائون02:56 +1d→05:10 +1d2h 14m10% on time · +1h 10mmakes up 6 min over this leg · 23 runs
- Allama Iqbal Express 10DN10علامہ اقبال ایکسپریس 10 ڈائون03:50 +1d→06:00 +1d2h 10m24% on time · +53 minmakes up 2 min over this leg · 35 runs
- Tezgam 8DN8تیزگام 8 ڈاؤن04:56 +1d→07:10 +1d2h 14m17% on time · +58 minno change over this leg · 37 runs
- Pak Business 34DN34پاک بزنس 34 ڈائون06:12 +1d→08:15 +1d2h 03m18% on time · +1h 05madds 2 min over this leg · 37 runs
- Millat Express 18DN18ملت ایکسپریس 18 ڈائون07:23 +1d→09:30 +1d2h 07m10% on time · +2h 37mmakes up 1 min over this leg · 38 runs
- Karachi Express 16DN16کراچی ایکسپریس 16 ڈائون08:12 +1d→10:15 +1d2h 03m13% on time · +2h 05mmakes up 4 min over this leg · 38 runs
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن11:25 +1d→13:45 +1d2h 20m13% on time · +2h 20mmakes up 12 min over this leg · 35 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون13:18 +1d→15:55 +1d2h 37m8% on time · +2h 09mmakes up 20 min over this leg · 38 runs
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن18:47 +1d→21:05 +1d2h 18m10% on time · +1h 17mmakes up 6 min over this leg · 36 runs
- Shalimar Express 28DN28شالیمار ایکسپریس 28 ڈائون22:10→00:05 +1d1h 55m44% on time · +22 minmakes up 7 min over this leg · 22 runs
Travelling the other way? Hyderabad Jn to Nawabshah Jn. trains →
Common questions
How many trains run from Nawabshah Jn. to Hyderabad Jn?
13 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Nawabshah Jn. to Hyderabad Jn?
Khyber Mail 2DN, booked at 1h 50m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Nawabshah Jn. to Hyderabad Jn is most likely to be on time?
Shalimar Express 28DN has the best recorded punctuality of the services we hold enough history for: 44% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 22 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 13 of 13 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Nawabshah Jn. to Hyderabad Jn?
Yes. 1 of the 13 scheduled services is booked to arrive on a later day than it departs: Shalimar Express 28DN.
Do trains lose time between Nawabshah Jn. and Hyderabad Jn?
Typically the opposite. Sukkur Express 146DN makes up about 42 min over this leg across 36 recorded runs. That does not mean it runs early; it means it arrived less late than it departed, which usually says more about how the timetable books this stretch than about the train.
How far is it from Nawabshah Jn. to Hyderabad Jn by train?
It is between 115 and 116 km along the track, depending on the service. Measured by summing our own GPS traces of trains running the route, not the straight-line distance between the two stations, which is always shorter than the rails. That is measured on 10 of the 13 services; the rest of the track on this route has not been traced yet.
Are these Nawabshah Jn. to Hyderabad Jn timings the real arrival times?
No. The departure and arrival columns are what the published timetable books. The delay columns beside them are what we recorded actually happening, from the operator's own reports and from GPS traces of the trains. Where a delay figure is blank we do not yet hold enough recorded runs to publish one.