Millat Express 17UP — the run of 22 August 2026
Reached Lala Musa Jn. at 22:30 on 23 August 2026, 196 minutes late — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 33 earlier stops
- Karachi CanttNo recordArrive—Depart17:00Delay—
- Drigh RoadCrossedArrive17:2218:34Depart17:2418:40Delay+1h 13m
- Hyderabad JnCrossedArrive19:4022:24Depart19:4822:33Delay+2h 44m
- ShahdadpurCrossedArrive21:0023:43Depart21:0223:46Delay+2h 44m
- Nawabshah Jn.CrossedArrive21:3200:22Depart21:3400:28Delay+2h 51m
- DaurCrossedArrive21:5200:56Depart21:5401:00Delay+3h 05m
- BandhiCrossedArrive22:0001:16Depart22:0201:18Delay+3h 17m
- Bhiria RoadCrossedArrive22:2301:53Depart22:2501:55Delay+3h 30m
- MehrabpurCrossedArrive22:5102:18Depart22:5302:21Delay+3h 28m
- Rohri Jn.CrossedArrive00:40 +1d03:29Depart01:05 +1d04:12Delay+2h 50m
- SadiqabadCrossedArrive03:23 +1d07:30Depart03:25 +1d07:34Delay+4h 07m
- Rahim Yar KhanCrossedArrive03:55 +1d07:57Depart03:57 +1d08:01Delay+4h 02m
- Khanpur Jn.CrossedArrive05:15 +1d08:46Depart05:17 +1d08:51Delay+3h 32m
- BahawalpurCrossedArrive06:50 +1d10:34Depart06:52 +1d10:38Delay+3h 45m
- Lodhran JnCrossedArrive07:15 +1d10:55Depart07:17 +1d10:58Delay+3h 40m
- DunyapurCrossedArrive07:46 +1d11:25Depart07:48 +1d11:28Delay+3h 40m
- JahaniaCrossedArrive08:10 +1d11:51Depart08:12 +1d11:55Delay+3h 41m
- Khanewal JnCrossedArrive08:40 +1d12:24Depart09:00 +1d12:50Delay+3h 45m
- Abdul HakimCrossedArrive09:35 +1d13:17Depart09:37 +1d13:20Delay+3h 42m
- Shorkot Cantt JnCrossedArrive10:03 +1d13:41Depart10:05 +1d13:47Delay+3h 38m
- Toba Tek SinghCrossedArrive10:30 +1d14:09Depart10:32 +1d14:12Delay+3h 39m
- GojraCrossedArrive11:04 +1d14:37Depart11:06 +1d14:46Delay+3h 34m
- FaisalabadCrossedArrive12:00 +1d15:30Depart12:30 +1d16:09Delay+3h 30m
- Chak Jhumra JnCrossedArrive12:59 +1d16:32Depart13:00 +1d16:35Delay+3h 34m
- ChiniotCrossedArrive13:28 +1d17:09Depart13:30 +1d17:12Delay+3h 42m
- Chanab NagarCrossedArrive13:40 +1d17:24Depart13:42 +1d17:26Delay+3h 45m
- Shaheenabad JnCrossedArrive14:35 +1d18:06Depart14:36 +1d18:09Delay+3h 31m
- Sargodha JnCrossedArrive15:30 +1d18:33Depart15:45 +1d18:49Delay+3h 04m
- BhalwalCrossedArrive16:34 +1d19:24Depart16:36 +1d19:27Delay+2h 51m
- PhularwanCrossedArrive17:00 +1d19:47Depart17:02 +1d19:49Delay+2h 48m
- Malakwal JnCrossedArrive17:35 +1d20:19Depart17:45 +1d20:32Delay+2h 44m
- Mandi BahauddinCrossedArrive18:15 +1d20:57Depart18:17 +1d21:04Delay+2h 43m
- Chilian WalaCrossedArrive18:33 +1d21:21Depart18:35 +1d21:47Delay+2h 49m
- DingaCrossedArrive18:48 +1d21:57Depart18:50 +1d22:00Delay+3h 10m
- Lala Musa Jn.CrossedArrive19:15 +1d22:30Depart—23:26Delay+3h 16m
Recorded times come from Pakistan Railways’ control room or from the train’s GPS.
The shape of the run
from the GPS trailWhere this run lost time, where it stood at a stop, and where its tracker went dark — the same journey as the table above, drawn from the raw position trail.
5,047 GPS positions recorded between 22 Aug 18:20 and 23 Aug 23:26 PKT · 34 of 35 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 0 of 34 stop-to-stop segments measured straight-line.
How late it was running — each step is a station
How long it stopped at each scheduled stop
What the marks mean
- A blank means the train’s tracker stopped reporting — it does not mean the train stopped or anything happened to it. 5 gaps on this run, 62 min total.
- 0 readings above 120 km/h, 0 not corroborated by the position trail. All values shown as recorded.
- Grey bar: how long the timetable allows here. Coloured bar: how long it actually stopped, with the figure printed under it. A stand longer than the scale is drawn capped and marked ▲ — the printed figure is always the recorded one. A dash means how long it stood there is unknown — not zero: either no departure was recorded, or the two recorded clocks contradict each other.
- An unwitnessed stop breaks the lateness line — it does not interpolate across it.
- Route distance is measured from traced track geometry where we have it, straight line between the two stations otherwise.
The upper trace above is recorded GPS positions; the lower trace is recorded station crossings — the same crossings shown in the table near the top of this page. A gap in one trace is not a gap in the other.