Lahore Jn. to Multan Cantt
Shalimar Express 28DN — within 15 minutes of the scheduled time 44% of the time, typically 22 minutes late, over 11 days of recorded runs across every stop of its full journey, not this segment alone.
Every train, compared
7 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Lahore 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 Lahore Jn. — no booked arrival at Lahore 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 |
|---|---|---|---|---|---|---|---|
| 116Musa Pak Express 116DN | 00:30 | 05:00 | 4h 30m | 334 km | +23 min | 33% | no data |
| 28Shalimar Express 28DN | 07:10 | 12:50 | 5h 40m | not measured yet | +22 min | 44% | no data |
| 2Khyber Mail 2DN | 07:35 +1d | 13:15 +1d | 5h 40m | 342 km | +2h 09m | 6% | adds 1h 12m · 14 |
| 8Tezgam 8DN | 13:45 | 18:50 | 5h 05m | 332 km | +52 min | 18% | adds 43 min · 38 |
| 40Jaffar Express 40DN | 16:45 | 21:55 | 5h 10m | 336 km | +50 min | 25% | adds 37 min · 24 |
| 16Karachi Express 16DN | 18:00 | 22:40 | 4h 40m | 335 km | +1h 59m | 17% | no data |
| 14Awam Express 14DN | 18:55 | 00:32 +1d | 5h 37m | 342 km | +2h 03m | 8% | adds 55 min · 35 |
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.
- Musa Pak Express 116DN116موسی پاک ایکسپریس 116 ڈاون00:30→05:004h 30m33% on time · +23 minno data over this leg
- Shalimar Express 28DN28شالیمار ایکسپریس 28 ڈائون07:10→12:505h 40m44% on time · +22 minno data over this leg
- Khyber Mail 2DN2خیبر میل 2 ڈائون07:35 +1d→13:15 +1d5h 40m6% on time · +2h 09madds 1h 12m over this leg · 14 runs
- Tezgam 8DN8تیزگام 8 ڈاؤن13:45→18:505h 05m18% on time · +52 minadds 43 min over this leg · 38 runs
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون16:45→21:555h 10m25% on time · +50 minadds 37 min over this leg · 24 runs
- Karachi Express 16DN16کراچی ایکسپریس 16 ڈائون18:00→22:404h 40m17% on time · +1h 59mno data over this leg
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون18:55→00:32 +1d5h 37m8% on time · +2h 03madds 55 min over this leg · 35 runs
Travelling the other way? Multan Cantt to Lahore Jn. trains →
Common questions
How many trains run from Lahore Jn. to Multan Cantt?
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 Lahore Jn. to Multan Cantt?
Musa Pak Express 116DN, booked at 4h 30m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Lahore Jn. to Multan Cantt 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. 7 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Lahore Jn. to Multan Cantt?
Yes. 1 of the 7 scheduled services is booked to arrive on a later day than it departs: Awam Express 14DN.
Do trains lose time between Lahore Jn. and Multan Cantt?
Typically yes. Khyber Mail 2DN adds about 1h 12m to its delay over this leg, measured across 14 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 Lahore Jn. to Multan Cantt by train?
It is between 332 and 342 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 6 of the 7 services; the rest of the track on this route has not been traced yet.
Are these Lahore 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.