latetrains.pkLate, on record40 live
Trains/Pakistan Express 45UP/22 August 2026

Pakistan Express 45UP — the run of 22 August 2026

The recorded journey of the run that departed Saturday 22 August 2026.
RouteKarachi Cantt → Rawalpindi
First recordedLandhi Jn., 14:41+7 min — names where it was first seen, not necessarily its origin
At Rawalpindi21:11+3h 36m

Reached Rawalpindi at 21:11 on 23 August 2026, 216 minutes late — from the operator's recorded crossing.

Every recorded crossing

this run only
Show the 31 earlier stops
  1. Karachi CanttNo recordArrive—Depart14:00Delay—
  2. Landhi Jn.CrossedArrive14:3514:41Depart14:3714:45Delay+7 min
  3. Hyderabad JnCrossedArrive16:4017:18Depart16:4817:27Delay+39 min
  4. Tando AdamCrossedArrive17:4918:19Depart17:5118:23Delay+31 min
  5. PadidanCrossedArrive19:0820:11Depart19:1020:16Delay+1h 03m
  6. KhairpurCrossedArrive20:4021:27Depart20:4221:30Delay+48 min
  7. Rohri Jn.CrossedArrive21:3522:06Depart22:0022:53Delay+31 min
  8. GhotkiCrossedArrive22:4300:25Depart22:4500:43Delay+1h 43m
  9. SadiqabadCrossedArrive00:06 +1d01:53Depart00:08 +1d01:58Delay+1h 48m
  10. Rahim Yar KhanCrossedArrive00:42 +1d02:19Depart00:44 +1d02:25Delay+1h 38m
  11. Khanpur Jn.CrossedArrive02:10 +1d03:06Depart02:15 +1d03:14Delay+57 min
  12. BahawalpurCrossedArrive03:50 +1d04:59Depart03:55 +1d05:04Delay+1h 09m
  13. Lodhran JnCrossedArrive04:14 +1d05:20Depart04:16 +1d05:23Delay+1h 06m
  14. Multan CanttCrossedArrive05:15 +1d06:31Depart05:40 +1d07:09Delay+1h 17m
  15. Khanewal JnCrossedArrive06:20 +1d08:11Depart06:25 +1d08:18Delay+1h 52m
  16. Abdul HakimCrossedArrive06:52 +1d08:44Depart06:54 +1d08:48Delay+1h 53m
  17. Shorkot Cantt JnCrossedArrive07:30 +1d09:13Depart07:35 +1d09:21Delay+1h 44m
  18. Toba Tek SinghCrossedArrive08:00 +1d09:44Depart08:02 +1d09:52Delay+1h 44m
  19. GojraCrossedArrive08:30 +1d10:22Depart08:32 +1d10:30Delay+1h 52m
  20. FaisalabadCrossedArrive09:30 +1d11:14Depart10:00 +1d12:02Delay+1h 45m
  21. Chak Jhumra JnCrossedArrive10:15 +1d12:28Depart10:17 +1d12:32Delay+2h 14m
  22. Sangla HillCrossedArrive10:36 +1d12:57Depart10:38 +1d13:01Delay+2h 22m
  23. SukhekeCrossedArrive11:02 +1d13:24Depart11:04 +1d14:08Delay+2h 22m
  24. HafizabadCrossedArrive11:45 +1d14:42Depart11:50 +1d14:46Delay+2h 58m
  25. Alipur ChathaCrossedArrive12:22 +1d15:14Depart12:24 +1d17:20Delay+2h 53m
  26. Wazirabad JnNo recordArrive13:25 +1dDepart13:30 +1dDelay—
  27. GujratNo recordArrive13:46 +1dDepart13:48 +1dDelay—
  28. Lala Musa Jn.CrossedArrive14:10 +1d17:28Depart14:12 +1d17:35Delay+3h 19m
  29. JhelumCrossedArrive14:43 +1d18:18Depart14:45 +1d18:21Delay+3h 36m
  30. DinaCrossedArrive15:03 +1d18:38Depart15:05 +1d18:41Delay+3h 36m
  31. Gujar KhanCrossedArrive16:12 +1d20:03Depart16:14 +1d20:06Delay+3h 51m
  1. ChaklalaCrossedArrive17:18 +1d20:59Depart17:20 +1d21:00Delay+3h 41m
  2. RawalpindiCrossedArrive17:35 +1d21:11Depart—21:32Delay+3h 36m

Recorded times come from Pakistan Railways’ control room or from the train’s GPS.

The shape of the run

from the GPS trail

Where 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.

8,241 GPS positions recorded between 22 Aug 14:06 and 23 Aug 21:57 PKT · 30 of 33 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 32 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, 92 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.