115 Musa Pak Express 115UP موسی پاک ایکسپریس 115 اپ
Running 32 min late — heading for Sahiwal, due 18:50 (operator's estimate), 109 km/h. Last crossed Chichawatni.
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.
8 days of recorded arrivals.
Over 28 recorded arrivals (2 Aug – 8 Oct 2026), Musa Pak Express 115UP has typically reached Lahore Jn. around 21:42 the day it leaves — on the worst one run in ten, past 22:51 the day it leaves, at Lahore Jn. itself. Today's run: track it live →
The “At Lahore Jn.” 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 5h — Multan Cantt to Lahore Jn.. Typically 5h 42m, 42 min longer.
What these figures cover
- Scheduled — the current timetable, Multan Cantt 16:00 to Lahore Jn. 21:00
- Typical journey — from the scheduled departure to the recorded arrival at Lahore Jn.; the median of 28 runs
- Bad day — 6h 51m 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 8 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 Multan CanttLeaves Multan Cantt 43 min early · reaches Lahore Jn. +42 min — +1h 25m lost along the way.
- Multan Cantt16:00ملتان کینٹ43 min early
- Khanewal Jn16:45خانیوال+8 min
- Mian Channu17:19مِياں چنُّوں+13 min
- Chichawatni17:47چِچہ وطنى+14 min
- Sahiwal18:20ساہِيوال+18 min
- Okara18:54اوکاڑا+20 min
- Pattoki19:30پتّوكى+24 min
- Raiwind Jn.20:03راۓوِنڈ جنکشن+34 min
- Kot Lakhpat20:29کوٹ لکھپت+46 min
- Lahore Jn.21:00لاہور جنکشن+42 min
Where it stands longest past the timetableshortest to longest recorded
- Sahiwalscheduled 2 min4–10 min
- Okarascheduled 2 min2–18 min
- Raiwind Jn.scheduled 2 min2–47 min
- Kot Lakhpatscheduled 2 min2–11 min
- Pattokischeduled 2 min2–12 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 Multan Cantt and Khanewal Jn (+51 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 | Multan Cantt | — | 16:00 |
| 2 | Khanewal Jn | 16:40 → 17:04·PR | 16:45 → 17:11 |
| 3 | Mian Channu | 17:17 → 17:45·PR | 17:19 → 17:48 |
| 4 | Chichawatni | 17:45 → 18:16·PR | 17:47 → 18:19 |
| 5 | Sahiwal | 18:18 | 18:20 |
| 6 | Okara | 18:52 | 18:54 |
| 7 | Pattoki | 19:28 | 19:30 |
| 8 | Raiwind Jn. | 20:01 | 20:03 |
| 9 | Kot Lakhpat | 20:27 | 20:29 |
| 10 | Lahore Jn. | 21:00 | — |
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: 23 August 2026 →
Station by station, last 5 days
39 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
2Khanewal Jnscheduled 16:40+7m5 days
Day Arrived Delay Recorded by Fri 9 Oct 17:04 +19m Pakistan Railways Thu 8 Oct arrived, time not recorded +29m Pakistan Railways Wed 7 Oct 16:52 +7m Pakistan Railways Tue 6 Oct 16:40 +3m Pakistan Railways Sun 4 Oct arrived, time not recorded +5m Pakistan Railways Seen on 5 of 5 days, ranging +3m to +29m. Every train at Khanewal Jn →
3Mian Channuscheduled 17:17+12m5 days
Day Arrived Delay Recorded by Fri 9 Oct 17:45 +27m Pakistan Railways Thu 8 Oct arrived, time not recorded +45m Pakistan Railways Wed 7 Oct 17:30 +12m Pakistan Railways Tue 6 Oct 17:19 on time Pakistan Railways Sun 4 Oct 17:27 +8m Pakistan Railways Seen on 5 of 5 days, ranging on time to +45m. Every train at Mian Channu →
4Chichawatnischeduled 17:45+13m5 days
Day Arrived Delay Recorded by Fri 9 Oct 18:16 +30m Pakistan Railways Thu 8 Oct 18:30 +44m Pakistan Railways Wed 7 Oct 17:59 +13m Pakistan Railways Tue 6 Oct 17:46 1m early Pakistan Railways Sun 4 Oct 17:55 +8m Pakistan Railways Seen on 5 of 5 days, ranging 1m early to +44m. Every train at Chichawatni →
5Sahiwalscheduled 18:18+15m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 19:04 +44m Pakistan Railways Wed 7 Oct 18:39 +19m Pakistan Railways Tue 6 Oct 18:30 +11m Pakistan Railways Sun 4 Oct 18:31 +11m Pakistan Railways Seen on 4 of 5 days, ranging +11m to +44m. Every train at Sahiwal →
6Okarascheduled 18:52+26m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 19:48 +54m Pakistan Railways Wed 7 Oct 19:15 +21m Pakistan Railways Tue 6 Oct 19:05 +12m Pakistan Railways Sun 4 Oct 19:24 +30m Pakistan Railways Seen on 4 of 5 days, ranging +12m to +54m. Every train at Okara →
7Pattokischeduled 19:28+28m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 20:30 +1h01 Pakistan Railways Wed 7 Oct 19:55 +25m Pakistan Railways Tue 6 Oct 19:44 +15m Pakistan Railways Sun 4 Oct 20:00 +30m Pakistan Railways Seen on 4 of 5 days, ranging +15m to +1h01. Every train at Pattoki →
8Raiwind Jn.scheduled 20:01+37m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 21:15 +1h14 Pakistan Railways Wed 7 Oct 20:44 +41m Pakistan Railways Tue 6 Oct 20:19 +18m Pakistan Railways Sun 4 Oct 20:35 +33m Pakistan Railways Seen on 4 of 5 days, ranging +18m to +1h14. Every train at Raiwind Jn. →
9Kot Lakhpatscheduled 20:27+48m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 22:11 +1h45 Pakistan Railways Wed 7 Oct 21:26 +57m Pakistan Railways Tue 6 Oct 20:54 +26m Pakistan Railways Sun 4 Oct 21:08 +39m Pakistan Railways Seen on 4 of 5 days, ranging +26m to +1h45. Every train at Kot Lakhpat →
10Lahore Jn.scheduled 21:00+56m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 22:58 +1h58 Train GPS Wed 7 Oct 22:04 +1h04 Train GPS Tue 6 Oct 21:28 +29m Train GPS Sun 4 Oct 21:47 +47m Train GPS Seen on 4 of 5 days, ranging +29m to +1h58. Every train at Lahore Jn. →
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 115UP usually late?
Typically 42 minutes late arriving at Lahore Jn., measured across 28 recorded arrivals (2 Aug – 8 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 115UP on a bad day?
On the worst one run in ten, 111 minutes late into Lahore Jn., against a typical 42 minutes late. Both come from the same 28 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 115UP leave Multan Cantt?
16:00, on the current published timetable. It is booked into Lahore Jn. at 21: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 115UP take from Multan Cantt to Lahore Jn.?
5h on the timetable. In practice a typical run has taken 5h 42m, measured from recorded arrivals at Lahore Jn..
How many stops does Musa Pak Express 115UP make?
10 on the current published timetable, from Multan Cantt to Lahore Jn.. 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.
Where is Musa Pak Express 115UP right now?
The live tracker for this train shows its last reported position and how late it was running at its most recent recorded stop. Position comes from the operator's own feed. When a train is not reporting we say so rather than estimating where it might be.
Other trains on this route
All Multan–Lahore 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.