Hyderabad Jn to Shahdadpur
Hazara Express 11UP — within 15 minutes of the scheduled time 24% of the time, typically 53 minutes late, over 8 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 Hyderabad Jn to Shahdadpur it typically adds 8 min, from 36 recorded runs. At Shahdadpur it has typically arrived 45 minutes late, from 42 recorded runs.
Every train, compared
5 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Hyderabad Jn and Shahdadpur 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 Hyderabad Jn — no booked arrival at Hyderabad Jn to measure from at all. Figures cover runs recorded between 30 July 2026 and 1 October 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 145Sukkur Express 145UP | 02:35 +1d | 03:55 +1d | 1h 20m | 73 km | — | — | adds 13 min · 34 |
| 11Hazara Express 11UP | 10:10 | 11:26 | 1h 16m | 73 km | +53 min | 24% | adds 8 min · 36 |
| 13Awam Express 13UP | 10:40 | 12:05 | 1h 25m | 73 km | +1h 50m | 5% | adds 9 min · 39 |
| 17Millat Express 17UP | 19:48 | 21:00 | 1h 12m | 72 km | +3h 34m | 0% | adds 9 min · 37 |
| 7Tezgam 7UP | 20:10 | 21:26 | 1h 16m | 73 km | +2h 13m | 4% | adds 10 min · 35 |
| 25Bahauddin Zikria Express 25UP | 22:00 | 23:11 | 1h 11m | 73 km | — | — | adds 12 min · 22 |
| 37Fareed Express 37UP | 23:00 | 00:20 +1d | 1h 20m | 73 km | +1h 25m | 6% | makes up 3 min · 28 |
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.
- Sukkur Express 145UP145سکھر ایکسپریس145اپ02:35 +1d→03:55 +1d1h 20mno delay figure yetadds 13 min over this leg · 34 runs
- Hazara Express 11UP11ہزارا ایکسپریس 11 اپ10:10→11:261h 16m24% on time · +53 minadds 8 min over this leg · 36 runs
- Awam Express 13UP13عوام ایکسپریس 13 اپ10:40→12:051h 25m5% on time · +1h 50madds 9 min over this leg · 39 runs
- Millat Express 17UP17ملت ایکسپریس 17 اپ19:48→21:001h 12m0% on time · +3h 34madds 9 min over this leg · 37 runs
- Tezgam 7UP7تيزگام 7 اپ20:10→21:261h 16m4% on time · +2h 13madds 10 min over this leg · 35 runs
- Bahauddin Zikria Express 25UP25بہائو الدین زکریا ایکسپری25 اپ22:00→23:111h 11mno delay figure yetadds 12 min over this leg · 22 runs
- Fareed Express 37UP37فرید ایکسپریس 37 اپ23:00→00:20 +1d1h 20m6% on time · +1h 25mmakes up 3 min over this leg · 28 runs
Travelling the other way? Shahdadpur to Hyderabad Jn trains →
Common questions
How many trains run from Hyderabad Jn to Shahdadpur?
7 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Hyderabad Jn to Shahdadpur?
Bahauddin Zikria Express 25UP, booked at 1h 11m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Hyderabad Jn to Shahdadpur is most likely to be on time?
Hazara Express 11UP has the best recorded punctuality of the services we hold enough history for: 24% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 53 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 5 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Hyderabad Jn to Shahdadpur?
Yes. 1 of the 7 scheduled services is booked to arrive on a later day than it departs: Fareed Express 37UP.
Do trains lose time between Hyderabad Jn and Shahdadpur?
Typically yes. Sukkur Express 145UP adds about 13 min to its delay over this leg, measured across 34 recorded runs. That is the CHANGE over the leg, not how late the train arrives: a train can run late its whole journey and add nothing here.
How far is it from Hyderabad Jn to Shahdadpur by train?
It is between 72 and 73 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.
Are these Hyderabad Jn to Shahdadpur 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.