Thall Express 129UP — the run of 18 August 2026
Reached Rawalpindi at 23:48 on 18 August 2026, 123 minutes late — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 37 earlier stops
- Multan CanttNo recordArrive—Depart06:30Delay—
- Sher Shah JnCrossedArrive06:4607:18Depart06:4707:21Delay+33 min
- MuzaffargarhCrossedArrive07:0307:44Depart07:0707:47Delay+41 min
- Mehmood KotCrossedArrive07:3508:26Depart07:3608:29Delay+51 min
- GurmaniCrossedArrive07:4808:40Depart07:4908:41Delay+52 min
- SanawanCrossedArrive08:0108:52Depart08:0208:53Delay+51 min
- Kot AdduCrossedArrive08:2109:10Depart08:2409:18Delay+49 min
- Dera DinpanahCrossedArrive08:3509:30Depart08:3609:32Delay+55 min
- Ahsan Pur AhpCrossedArrive08:4709:41Depart08:4809:43Delay+54 min
- Kot SultanCrossedArrive09:0409:55Depart09:0509:57Delay+52 min
- LayyahCrossedArrive09:2710:18Depart09:3210:24Delay+52 min
- DorattaCrossedArrive09:4610:54Depart09:4710:55Delay+1h 08m
- Karor Lal EsanCrossedArrive10:0211:12Depart10:0411:15Delay+1h 10m
- BehalCrossedArrive10:2411:39Depart10:2511:41Delay+1h 16m
- BhakkarCrossedArrive10:4212:11Depart10:4412:17Delay+1h 29m
- Darya KhanCrossedArrive11:1812:40Depart11:2012:42Delay+1h 23m
- Shah AlamCrossedArrive12:0213:10Depart12:0313:11Delay+1h 08m
- Kalur KotCrossedArrive12:4513:52Depart12:4713:55Delay+1h 08m
- PiplanCrossedArrive13:1714:28Depart13:1914:34Delay+1h 11m
- AlluwaliCrossedArrive13:4314:47Depart13:44Delay+1h 05m
- Kundian JnCrossedArrive14:1515:09Depart14:3515:44Delay+54 min
- Mian WaliCrossedArrive14:5316:06Depart14:5816:09Delay+1h 14m
- Pai KhelCrossedArrive15:1916:42Depart15:2016:44Delay+1h 24m
- Daud Khel JnCrossedArrive15:3417:07Depart15:3517:10Delay+1h 33m
- Mukhad RoadCrossedArrive16:3018:08Depart16:3118:12Delay+1h 39m
- InjraNo recordArrive16:50Depart16:51Delay—
- KhatakbadCrossedArrive17:0418:48Depart17:05Delay+1h 45m
- ChhabCrossedArrive17:2019:02Depart17:2119:04Delay+1h 42m
- JhammatCrossedArrive17:3619:18Depart17:37Delay+1h 42m
- Jand JnCrossedArrive18:2019:56Depart18:2220:04Delay+1h 37m
- DomelCrossedArrive18:5620:32Depart18:5720:34Delay+1h 36m
- Basal JnCrossedArrive19:0820:39Depart19:09Delay+1h 32m
- Attock City JnCrossedArrive20:0021:26Depart20:0521:31Delay+1h 26m
- FaqirabadCrossedArrive20:2022:01Depart20:2122:03Delay+1h 42m
- Hasan AbdalCrossedArrive20:3722:25Depart20:3922:27Delay+1h 49m
- WahCrossedArrive20:4422:33Depart20:4522:38Delay+1h 50m
- Taxila CanttCrossedArrive21:0022:54Depart21:0222:55Delay+1h 54m
- Golra SharifCrossedArrive21:2723:23Depart21:2923:28Delay+1h 57m
- RawalpindiCrossedArrive21:4523:48Depart21:4500:03Delay+2h 03m
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.
3,678 GPS positions recorded between 18 Aug 06:05 and 19 Aug 00:14 PKT · 37 of 39 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 1 of 38 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. 7 gaps on this run, 84 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.