latetrains.pkLate, on record38 live
Trains/Tezgam 7UP/22 August 2026

Tezgam 7UP — the run of 22 August 2026

The recorded journey of the run that departed Saturday 22 August 2026.
RouteKarachi Cantt → Rawalpindi
First recordedHyderabad Jn, 21:25+1h 23m — names where it was first seen, not necessarily its origin
At Rawalpindithe record stops before Rawalpindi — last recorded at Gujar Khan

The record stops before Rawalpindi — last recorded at Gujar Khan at 00:07.

Every recorded crossing

this run only
Show the 25 earlier stops
  1. Karachi CanttNo recordArrive—Depart17:30Delay—
  2. Hyderabad JnCrossedArrive20:0221:25Depart20:1021:39Delay+1h 23m
  3. Tando AdamCrossedArrive21:0722:31Depart21:0922:34Delay+1h 24m
  4. ShahdadpurCrossedArrive21:2622:54Depart21:2822:57Delay+1h 28m
  5. Nawabshah Jn.CrossedArrive21:5723:33Depart22:0023:38Delay+1h 37m
  6. MehrabpurCrossedArrive23:0901:14Depart23:1101:37Delay+2h 06m
  7. KhairpurCrossedArrive00:10 +1d02:29Depart00:12 +1d02:32Delay+2h 20m
  8. Rohri Jn.CrossedArrive01:35 +1d03:10Depart02:00 +1d03:50Delay+1h 35m
  9. GhotkiCrossedArrive02:39 +1d05:36Depart02:41 +1d05:51Delay+2h 57m
  10. Rahim Yar KhanCrossedArrive04:34 +1d07:22Depart04:36 +1d07:31Delay+2h 49m
  11. Khanpur Jn.CrossedArrive05:35 +1d08:18Depart05:40 +1d08:26Delay+2h 43m
  12. BahawalpurCrossedArrive07:16 +1d10:18Depart07:20 +1d10:25Delay+3h 03m
  13. Multan CanttCrossedArrive08:35 +1d11:33Depart08:55 +1d12:08Delay+2h 58m
  14. Khanewal JnCrossedArrive09:35 +1d12:51Depart09:40 +1d13:02Delay+3h 17m
  15. Mian ChannuCrossedArrive10:12 +1d13:32Depart10:14 +1d13:35Delay+3h 20m
  16. ChichawatniCrossedArrive10:40 +1d13:59Depart10:42 +1d14:03Delay+3h 20m
  17. SahiwalCrossedArrive11:23 +1d14:37Depart11:25 +1d14:40Delay+3h 14m
  18. OkaraCrossedArrive11:52 +1d15:17Depart11:54 +1d15:22Delay+3h 25m
  19. PattokiCrossedArrive12:26 +1d15:52Depart12:28 +1d16:01Delay+3h 26m
  20. Raiwind Jn.CrossedArrive13:00 +1d16:53Depart13:05 +1d16:56Delay+3h 54m
  21. Lahore Jn.CrossedArrive14:00 +1d17:42Depart14:30 +1d18:30Delay+3h 43m
  22. GujranwalaCrossedArrive15:25 +1d19:43Depart15:30 +1d19:48Delay+4h 18m
  23. Wazirabad JnNo recordArrive15:55 +1dDepart15:57 +1dDelay—
  24. GujratCrossedArrive16:13 +1d21:29Depart16:15 +1d21:39Delay+5h 16m
  25. Lala Musa Jn.No recordArrive16:47 +1dDepart16:49 +1dDelay—
  1. JhelumCrossedArrive17:31 +1d22:38Depart17:33 +1d22:43Delay+5h 08m
  2. Gujar KhanCrossedArrive18:48 +1d00:07Depart18:50 +1d00:12Delay+5h 19m
  1. ChaklalaNo recordArrive19:45 +1dDepart19:47 +1dDelay—
  1. RawalpindiNo recordArrive20:00 +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,601 GPS positions recorded between 22 Aug 17:38 and 24 Aug 01:22 PKT · 24 of 29 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 28 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. 15 gaps on this run, 161 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.