Hyderabad Jn to Karachi City
Sukkur Express 146DN — within 15 minutes of the scheduled time 39% of the time, typically 19 minutes late, over 9 days of recorded runs across every stop of its full journey, not this segment alone. At Karachi City it has typically arrived 72 minutes late, from 9 recorded runs.
Every train, compared
5 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Hyderabad Jn and Karachi City 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 4 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 146Sukkur Express 146DN | 04:10 +1d | 07:55 +1d | 3h 45m | not measured yet | +19 min | 39% | no data |
| 38Fareed Express 38DN | 04:35 +1d | 08:20 +1d | 3h 45m | not measured yet | +44 min | 14% | no data |
| 26Bahauddin Zikria Express 26DN | 05:20 +1d | 08:55 +1d | 3h 35m | 177 km | +1h 10m | 10% | adds 43 min · 8 |
| 150Mehran Express 150DN | 07:55 | 11:15 | 3h 20m | not measured yet | — | — | no data |
| 152Shah Latif Express 152DN | 16:30 | 20:10 | 3h 40m | 179 km | +1h 22m | 6% | adds 1h 06m · 15 |
| 12Hazara Express 12DN | 21:15 +1d | 00:45 +2d | 3h 30m | 177 km | +1h 17m | 10% | adds 23 min · 16 |
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 146DN146سکھر ایکسپریس146ڈاؤن04:10 +1d→07:55 +1d3h 45m39% on time · +19 minno data over this leg
- Fareed Express 38DN38فرید ایکسپریس 38 ڈائون04:35 +1d→08:20 +1d3h 45m14% on time · +44 minno data over this leg
- Bahauddin Zikria Express 26DN26بہائو الدین زکریا ایکسپریس26 ڈائون05:20 +1d→08:55 +1d3h 35m10% on time · +1h 10madds 43 min over this leg · 8 runs
- Mehran Express 150DN150مہران ایکسپریس 150ڈاؤن07:55→11:153h 20mno delay figure yetno data over this leg
- Shah Latif Express 152DN152شاھ لطیف ایکسپریس152ڈاؤن16:30→20:103h 40m6% on time · +1h 22madds 1h 06m over this leg · 15 runs
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن21:15 +1d→00:45 +2d3h 30m10% on time · +1h 17madds 23 min over this leg · 16 runs
Travelling the other way? Karachi City to Hyderabad Jn trains →
Common questions
How many trains run from Hyderabad Jn to Karachi City?
6 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 Karachi City?
Mehran Express 150DN, booked at 3h 20m 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 Karachi City is most likely to be on time?
Sukkur Express 146DN has the best recorded punctuality of the services we hold enough history for: 39% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 19 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 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Hyderabad Jn to Karachi City?
Yes. 1 of the 6 scheduled services is booked to arrive on a later day than it departs: Hazara Express 12DN.
Do trains lose time between Hyderabad Jn and Karachi City?
Typically yes. Shah Latif Express 152DN adds about 1h 06m to its delay over this leg, measured across 15 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 Karachi City by train?
It is between 177 and 179 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 3 of the 6 services; the rest of the track on this route has not been traced yet.
Are these Hyderabad Jn to Karachi City 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.