Landhi Jn. to Multan Cantt
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 Landhi Jn. to Multan Cantt it typically adds 58 min, from 36 recorded runs. At Multan Cantt it has typically arrived 53 minutes late, from 45 recorded runs.
Every train, compared
6 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Landhi Jn. and Multan Cantt 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 Landhi Jn. — no booked arrival at Landhi Jn. to measure from at all. Figures cover runs recorded between 30 July 2026 and 7 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 11Hazara Express 11UP | 07:50 | 00:10 +1d | 16h 20m | 912 km | +45 min | 27% | adds 58 min · 36 |
| 13Awam Express 13UP | 08:18 | 01:35 +1d | 17h 17m | 915 km | +1h 42m | 6% | adds 1h 43m · 38 |
| 47Rehman Baba Express 47UP | 12:42 | 03:20 +1d | 14h 38m | 909 km | +1h 43m | 10% | adds 1h 53m · 35 |
| 45Pakistan Express 45UP | 14:37 | 05:15 +1d | 14h 38m | 907 km | +2h 25m | 2% | adds 1h 54m · 35 |
| 25Bahauddin Zikria Express 25UP | 19:34 | 10:35 +1d | 15h 01m | 913 km | +1h 52m | 5% | adds 2h 42m · 11 |
| 1Khyber Mail 1UP | 22:58 | 13:30 +1d | 14h 32m | 913 km | +1h 39m | 9% | adds 3h 12m · 33 |
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.
- Hazara Express 11UP11ہزارا ایکسپریس 11 اپ07:50→00:10 +1d16h 20m27% on time · +45 minadds 58 min over this leg · 36 runs
- Awam Express 13UP13عوام ایکسپریس 13 اپ08:18→01:35 +1d17h 17m6% on time · +1h 42madds 1h 43m over this leg · 38 runs
- Rehman Baba Express 47UP47رحمان بابا ایکسپریس47اپ12:42→03:20 +1d14h 38m10% on time · +1h 43madds 1h 53m over this leg · 35 runs
- Pakistan Express 45UP45پاکستان ایکسپریس 45 اپ14:37→05:15 +1d14h 38m2% on time · +2h 25madds 1h 54m over this leg · 35 runs
- Bahauddin Zikria Express 25UP25بہائو الدین زکریا ایکسپری25 اپ19:34→10:35 +1d15h 01m5% on time · +1h 52madds 2h 42m over this leg · 11 runs
- Khyber Mail 1UP1خیبر میل 1 اپ22:58→13:30 +1d14h 32m9% on time · +1h 39madds 3h 12m over this leg · 33 runs
Travelling the other way? Multan Cantt to Landhi Jn. trains →
Common questions
How many trains run from Landhi Jn. to Multan Cantt?
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 Landhi Jn. to Multan Cantt?
Khyber Mail 1UP, booked at 14h 32m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Landhi Jn. to Multan Cantt 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. 6 of 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Landhi Jn. to Multan Cantt?
Yes. All 6 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 Landhi Jn. and Multan Cantt?
Typically yes. Khyber Mail 1UP adds about 3h 12m 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 Landhi Jn. to Multan Cantt by train?
It is between 907 and 915 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 Landhi Jn. to Multan Cantt 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.