Hyderabad Jn to Khanewal Jn
Hazara Express 11UP — within 15 minutes of the scheduled time 27% of the time, typically 45 minutes late, over 12 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 Khanewal Jn it typically adds 28 min, from 28 recorded runs. At Khanewal Jn it has typically arrived 72 minutes late, from 25 recorded runs.
Every train, compared
12 of 15 with 7+ daysOver this leg is the CHANGE in a train's delay between Hyderabad Jn and Khanewal 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 Hyderabad Jn — no booked arrival at Hyderabad Jn to measure from at all. Figures cover runs recorded between 30 July 2026 and 6 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 5Green Line 5UP | 00:40 +1d | 11:45 +1d | 11h 05m | 759 km | +41 min | 27% | adds 54 min · 38 |
| 1Khyber Mail 1UP | 01:10 +1d | 14:25 +1d | 13h 15m | 811 km | +1h 39m | 9% | adds 2h 23m · 33 |
| 27Shalimar Express 27UP | 09:25 | — | — | 811 km | +59 min | 21% | no data |
| 11Hazara Express 11UP | 10:10 | 01:20 +1d | 15h 10m | 808 km | +45 min | 27% | adds 28 min · 28 |
| 13Awam Express 13UP | 10:40 | 02:35 +1d | 15h 55m | 812 km | +1h 42m | 6% | adds 41 min · 38 |
| 47Rehman Baba Express 47UP | 14:55 | 04:21 +1d | 13h 26m | 807 km | +1h 43m | 10% | adds 1h 37m · 36 |
| 45Pakistan Express 45UP | 16:48 | 06:20 +1d | 13h 32m | 805 km | +2h 25m | 2% | adds 1h 14m · 35 |
| 41Karakoram Express 41UP | 17:40 | 04:45 +1d | 11h 05m | 759 km | — | — | adds 52 min · 29 |
| 9Allama Iqbal Express 9UP | 18:20 | 07:25 +1d | 13h 05m | 762 km | +2h 52m | 5% | adds 55 min · 33 |
| 33Pak Business 33UP | 18:40 | 06:05 +1d | 11h 25m | 758 km | +2h 01m | 10% | adds 1h 01m · 33 |
| 17Millat Express 17UP | 19:48 | 08:40 +1d | 12h 52m | 762 km | +3h 35m | 0% | adds 49 min · 35 |
| 7Tezgam 7UP | 20:10 | 09:35 +1d | 13h 25m | 803 km | +1h 59m | 5% | adds 1h 10m · 35 |
| 15Karachi Express 15UP | 20:40 | 08:55 +1d | 12h 15m | 806 km | +1h 45m | 10% | adds 1h 05m · 35 |
| 43Shah Hussain Express 43UP | 23:35 | 10:30 +1d | 10h 55m | 759 km | — | — | no data |
| 35Sir Sayyed Express 35UP | 23:45 | 10:55 +1d | 11h 10m | 759 km | — | — | no data |
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.
- Green Line 5UP5گرين لائن5 اپ00:40 +1d→11:45 +1d11h 05m27% on time · +41 minadds 54 min over this leg · 38 runs
- Khyber Mail 1UP1خیبر میل 1 اپ01:10 +1d→14:25 +1d13h 15m9% on time · +1h 39madds 2h 23m over this leg · 33 runs
- Shalimar Express 27UP27شالیمار ایکسپریس 27 اپ09:25→——21% on time · +59 minno data over this leg
- Hazara Express 11UP11ہزارا ایکسپریس 11 اپ10:10→01:20 +1d15h 10m27% on time · +45 minadds 28 min over this leg · 28 runs
- Awam Express 13UP13عوام ایکسپریس 13 اپ10:40→02:35 +1d15h 55m6% on time · +1h 42madds 41 min over this leg · 38 runs
- Rehman Baba Express 47UP47رحمان بابا ایکسپریس47اپ14:55→04:21 +1d13h 26m10% on time · +1h 43madds 1h 37m over this leg · 36 runs
- Pakistan Express 45UP45پاکستان ایکسپریس 45 اپ16:48→06:20 +1d13h 32m2% on time · +2h 25madds 1h 14m over this leg · 35 runs
- Karakoram Express 41UP41قراقرم ایکسپریس 41 اپ17:40→04:45 +1d11h 05mno delay figure yetadds 52 min over this leg · 29 runs
- Allama Iqbal Express 9UP9علامہ اقبال ایکسپریس 9 اپ18:20→07:25 +1d13h 05m5% on time · +2h 52madds 55 min over this leg · 33 runs
- Pak Business 33UP33پاک بزنس 33 اپ18:40→06:05 +1d11h 25m10% on time · +2h 01madds 1h 01m over this leg · 33 runs
- Millat Express 17UP17ملت ایکسپریس 17 اپ19:48→08:40 +1d12h 52m0% on time · +3h 35madds 49 min over this leg · 35 runs
- Tezgam 7UP7تيزگام 7 اپ20:10→09:35 +1d13h 25m5% on time · +1h 59madds 1h 10m over this leg · 35 runs
- Karachi Express 15UP15کراچی ایکسپریس 15 اپ20:40→08:55 +1d12h 15m10% on time · +1h 45madds 1h 05m over this leg · 35 runs
- Shah Hussain Express 43UP43شاہ حسین ایکسپریس 43اپ23:35→10:30 +1d10h 55mno delay figure yetno data over this leg
- Sir Sayyed Express 35UP35سر سید ایکپریس 35اپ23:45→10:55 +1d11h 10mno delay figure yetno data over this leg
Travelling the other way? Khanewal Jn to Hyderabad Jn trains →
Common questions
How many trains run from Hyderabad Jn to Khanewal Jn?
15 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 Khanewal Jn?
Shah Hussain Express 43UP, booked at 10h 55m 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 Khanewal Jn is most likely to be on time?
Hazara Express 11UP has the best recorded punctuality of the services we hold enough history for: 27% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 45 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 12 of 15 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Hyderabad Jn to Khanewal Jn?
Yes. 12 of the 15 scheduled services are booked to arrive on a later day than they depart: Hazara Express 11UP, Awam Express 13UP, Rehman Baba Express 47UP, Pakistan Express 45UP and others.
Do trains lose time between Hyderabad Jn and Khanewal Jn?
Typically yes. Khyber Mail 1UP adds about 2h 23m to its delay over this leg, measured across 33 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 Khanewal Jn by train?
It is between 758 and 812 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 Khanewal 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.