latetrains.pkLate, on record53 live
Trains/Tezgam 8DN/22 August 2026

Tezgam 8DN — the run of 22 August 2026

The recorded journey of the run that departed Saturday 22 August 2026.
RouteRawalpindi → Karachi Cantt
First recordedJhelum, 10:16+11 min — names where it was first seen, not necessarily its origin
At Karachi Canttthe record stops before Karachi Cantt — last recorded at Drigh Road

The record stops before Karachi Cantt — last recorded at Drigh Road at 13:15.

Every recorded crossing

this run only
Show the 28 earlier stops
  1. RawalpindiNo recordArrive—Depart08:00Delay—
  2. ChaklalaNo recordArrive08:09Depart08:11Delay—
  3. Gujar KhanNo recordArrive08:52Depart08:54Delay—
  4. JhelumCrossedArrive10:0610:16Depart10:0810:19Delay+11 min
  5. Lala Musa Jn.CrossedArrive11:0011:03Depart11:0511:08Delay+4 min
  6. GujratCrossedArrive11:2211:29Depart11:2411:32Delay+7 min
  7. Wazirabad JnCrossedArrive11:4011:45Depart11:4211:49Delay+5 min
  8. GujranwalaCrossedArrive12:1012:19Depart12:1512:24Delay+9 min
  9. Lahore Jn.CrossedArrive13:1513:23Depart13:4514:12Delay+9 min
  10. Raiwind Jn.CrossedArrive14:2014:57Depart14:2515:01Delay+37 min
  11. PattokiCrossedArrive14:5615:32Depart14:5815:34Delay+37 min
  12. OkaraCrossedArrive15:4116:06Depart15:4316:12Delay+25 min
  13. SahiwalCrossedArrive16:2716:44Depart16:2916:51Delay+18 min
  14. ChichawatniCrossedArrive17:0017:19Depart17:0217:22Delay+19 min
  15. Mian ChannuCrossedArrive17:2817:45Depart17:3018:03Delay+18 min
  16. Khanewal JnCrossedArrive18:1018:35Depart18:1518:57Delay+25 min
  17. Multan CanttCrossedArrive18:5019:33Depart19:1020:08Delay+44 min
  18. BahawalpurCrossedArrive20:2521:49Depart20:2921:53Delay+1h 24m
  19. Khanpur Jn.CrossedArrive22:1023:43Depart22:1523:57Delay+1h 33m
  20. Rahim Yar KhanCrossedArrive22:4700:45Depart22:4900:51Delay+1h 58m
  21. GhotkiCrossedArrive00:23 +1d03:22Depart00:25 +1d03:25Delay+2h 59m
  22. Rohri Jn.CrossedArrive01:30 +1d04:25Depart01:55 +1d05:04Delay+2h 56m
  23. KhairpurCrossedArrive02:22 +1d05:29Depart02:24 +1d05:31Delay+3h 08m
  24. MehrabpurCrossedArrive03:02 +1d06:10Depart03:04 +1d06:14Delay+3h 09m
  25. Nawabshah Jn.CrossedArrive04:54 +1d07:58Depart04:56 +1d08:02Delay+3h 05m
  26. ShahdadpurCrossedArrive05:47 +1d08:36Depart05:49 +1d08:40Delay+2h 50m
  27. Tando AdamCrossedArrive06:22 +1d09:00Depart06:24 +1d09:06Delay+2h 39m
  28. Hyderabad JnCrossedArrive07:10 +1d10:04Depart07:15 +1d10:24Delay+2h 55m
  1. Landhi Jn.CrossedArrive09:15 +1d12:39Depart09:17 +1d12:52Delay+3h 25m
  2. Drigh RoadCrossedArrive09:55 +1d13:15Depart09:57 +1d13:18Delay+3h 20m
  3. Karachi CanttNo recordArrive10:30 +1dDepart—Delay—

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.

4,403 GPS positions recorded between 22 Aug 09:24 and 23 Aug 13:39 PKT · 27 of 31 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 30 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. 2 gaps on this run, 55 min total.
  • 4 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.