116 Musa Pak Express 116DN موسی پاک ایکسپریس 116 ڈاون
How late is it, usually?
median per recorded stop arrivalEvery figure here is a median, not an average: why we publish a median, not an average. What counts as on time, and why some figures here are blank, is set out in what on time means here, and every threshold behind it.
7 days of recorded arrivals.
Over 19 recorded arrivals (2 Aug – 9 Oct 2026), Musa Pak Express 116DN has typically reached Multan Cantt around 05:29 the day it leaves — on the worst one run in ten, past 06:13 the day it leaves, at Multan Cantt itself.
The “At Multan Cantt” tile above is the arrival at the end of the run; “Typical delay, any stop” averages every stop including the earlier ones, so it usually reads smaller. Where the time goes, below, shows every stop we have recorded.
How long does it take?
scheduled vs recordedScheduled 4h 30m — Lahore Jn. to Multan Cantt. Typically 4h 59m, 29 min longer.
What these figures cover
- Scheduled — the current timetable, Lahore Jn. 00:30 to Multan Cantt 05:00
- Typical journey — from the scheduled departure to the recorded arrival at Multan Cantt; the median of 19 runs
- Bad day — 5h 43m at the 90th percentile: nine runs in ten come in under it
- Keyline — the scheduled time. The solid bar is the typical journey, the faint bar behind it the bad day.
- Recorded arrivals: 2 August to 9 October 2026.
- End to end. For a shorter leg, the stop times are in the timetable below.
Which day is worst?
mean minutes late per recorded arrival, 8-week windowThis is a mean over an 8-week window, not the median (typical) figure above — the two are not directly comparable.
Where the time goes
most of it lost after Lahore Jn.Leaves Lahore Jn. 10 min early · reaches Multan Cantt +29 min — +39 min lost along the way.
- Lahore Jn.00:30لاہور جنکشن10 min early
- Raiwind Jn.01:06راۓوِنڈ جنکشن+28 min
- Okara02:11اوکاڑا+30 min
- Sahiwal02:50ساہِيوال+26 min
- Khanewal Jn04:20خانیوال+23 min
- Multan Cantt05:00ملتان کینٹ+29 min
Where it stands longest past the timetableshortest to longest recorded
- Khanewal Jnscheduled 5 min4–22 min
- Okarascheduled 2 min2–11 min
- Raiwind Jn.scheduled 2 min2–10 min
- Sahiwalscheduled 2 min2–7 min
What the marks mean
- Solid bar — the typical delay at that stop (median of recorded arrivals)
- Faint bar behind — the bad day (90th percentile): worse than nine tenths of recorded arrivals here
- No faint bar — fewer than 7 recorded arrivals at that stop, too thin for a 90th percentile. The solid bar can still show: it needs only 3.
- — (no solid bar either) — fewer than 3 recorded runs at that stop
- A negative figure means the train typically ran early at that stop, not late
- Band — the shortest and the longest stand recorded at that stop. The train has left as early as the first figure.
- Keyline — the scheduled stop, arrival to departure on the timetable below.
- Why a train stands is not recorded — a crossing, a loco change and a red signal all look the same on the clock.
- The five stops that stand longest past the timetable, not every stop — most routes have more. A stop qualifies with 7 or more runs timed in and out, and is skipped where the timetable books no stop, books one over an hour, or where any recorded stand ran past three hours.
- Most time is lost between Lahore Jn. and Raiwind Jn. (+38 min)
- Every stop on the current timetable is listed, in order, measured or not.
Timetable
scheduled → actual, 9 October 2026 runThe second time in a cell is what actually happened on the 9 October 2026 run.
| # | Station | Arrival | Departure |
|---|---|---|---|
| 1 | Lahore Jn. | — | 00:30 |
| 2 | Raiwind Jn. | 01:04 → 01:33·PR | 01:06 |
| 3 | Okara | 02:09 → 02:32·PR | 02:11 |
| 4 | Sahiwal | 02:48 → 03:02·PR | 02:50 |
| 5 | Khanewal Jn | 04:15 → 04:17·PR | 04:20 → 04:22 |
| 6 | Multan Cantt | 05:00 → 05:03 | — → 05:06 |
What the marks mean
- → 21:28 — actual time on the 9 October 2026 run
- ·PR — Pakistan Railways' own record; unmarked is from the train's GPS
- +1d — the stop falls on a later day of the train's own run, counting from the day it starts. It is not a date.
- Blank — not recorded
A full recorded run: 22 August 2026 →
Station by station, last 5 days
25 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
2Raiwind Jn.scheduled 01:04+27m5 days
Day Arrived Delay Recorded by Fri 9 Oct 01:33 +27m Pakistan Railways Wed 7 Oct 01:35 +29m Pakistan Railways Tue 6 Oct 01:37 +32m Pakistan Railways Sun 4 Oct 01:28 +22m Pakistan Railways Fri 2 Oct 01:28 +23m Pakistan Railways Seen on 5 of 5 days, ranging +22m to +32m. Every train at Raiwind Jn. →
3Okarascheduled 02:09+21m5 days
Day Arrived Delay Recorded by Fri 9 Oct 02:32 +21m Pakistan Railways Wed 7 Oct 02:40 +30m Pakistan Railways Tue 6 Oct 02:47 +37m Pakistan Railways Sun 4 Oct 02:29 +19m Pakistan Railways Fri 2 Oct 02:31 +20m Pakistan Railways Seen on 5 of 5 days, ranging +19m to +37m. Every train at Okara →
4Sahiwalscheduled 02:48+15m5 days
Day Arrived Delay Recorded by Fri 9 Oct 03:02 +12m Pakistan Railways Wed 7 Oct 03:20 +32m Pakistan Railways Tue 6 Oct 03:20 +32m Pakistan Railways Sun 4 Oct 02:58 +8m Pakistan Railways Fri 2 Oct 03:04 +15m Pakistan Railways Seen on 5 of 5 days, ranging +8m to +32m. Every train at Sahiwal →
5Khanewal Jnscheduled 04:15+23m5 days
Day Arrived Delay Recorded by Fri 9 Oct 04:17 3m early Pakistan Railways Wed 7 Oct 04:56 +37m Pakistan Railways Tue 6 Oct arrived, time not recorded +31m Pakistan Railways Sun 4 Oct 04:28 +8m Pakistan Railways Fri 2 Oct 04:43 +23m Pakistan Railways Seen on 5 of 5 days, ranging 3m early to +37m. Every train at Khanewal Jn →
6Multan Canttscheduled 05:00+31m5 days
Day Arrived Delay Recorded by Fri 9 Oct 05:03 +4m Train GPS Wed 7 Oct 05:50 +51m Train GPS Tue 6 Oct 06:10 +1h10 Train GPS Sun 4 Oct 05:30 +31m Train GPS Fri 2 Oct 05:26 +26m Train GPS Seen on 5 of 5 days, ranging +4m to +1h10. Every train at Multan Cantt →
What the marks mean
- Tap a station — each day’s arrival, delay and recorder
- Green — within 15 minutes of the scheduled time
- Amber — 16 to 45 minutes late
- Red — over 45 minutes late
- Hollow — not recorded that day
- Grey — arrived, no delay figure
- Dash (—) — no delay figure for this stop yet
- Pakistan Railways — its own arrival record; Train GPS — measured from the train’s position
- The starting station is not listed — a train does not arrive where it begins.
Common questions
Is Musa Pak Express 116DN usually late?
Typically 29 minutes late arriving at Multan Cantt, measured across 19 recorded arrivals (2 Aug – 9 Oct 2026). That is the median, so half its runs were better than that and half were worse. It is what we recorded happening, not what the timetable books.
How late is Musa Pak Express 116DN on a bad day?
On the worst one run in ten, 73 minutes late into Multan Cantt, against a typical 29 minutes late. Both come from the same 19 recorded arrivals. A bad day is not the worst day we have ever seen; it is the level one run in ten reaches or passes.
What time does Musa Pak Express 116DN leave Lahore Jn.?
00:30, on the current published timetable. It is booked into Multan Cantt at 05:00, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.
How long does Musa Pak Express 116DN take from Lahore Jn. to Multan Cantt?
4h 30m on the timetable. In practice a typical run has taken 4h 59m, measured from recorded arrivals at Multan Cantt.
How many stops does Musa Pak Express 116DN make?
6 on the current published timetable, from Lahore Jn. to Multan Cantt. The full stop list, with the times booked at each one, is in the timetable on this page. Not every stop is recorded on every run: we publish arrivals we actually observed rather than filling the gaps.
Other trains on this route
All Lahore–Multan trains →Service history (first year, operating eras) is drawn from Wikipedia's List of Pakistan Railways trains, retrieved 15 August 2026, matched on train number. Further reading: the train's own Wikipedia article.