latetrains.pkLate, on record42 live
Trains/Jaffar Express 39UP/22 August 2026

Jaffar Express 39UP — the run of 22 August 2026

The recorded journey of the run that departed Saturday 22 August 2026.
RouteJacobabad Jn → Peshawar Cantt
First recordedSukkur, 21:03+1h 03m — names where it was first seen, not necessarily its origin
At Peshawar Cantt23:00+3h 26m

Reached Peshawar Cantt at 23:00 on 23 August 2026, 206 minutes late — from the operator's recorded crossing.

Every recorded crossing

this run only
Show the 34 earlier stops
  1. Jacobabad JnNo recordArrive—Depart17:50Delay—
  2. ShikarpurNo recordArrive19:00Depart19:05Delay—
  3. SukkurCrossedArrive20:0021:03Depart20:0521:13Delay+1h 03m
  4. Rohri Jn.CrossedArrive20:2521:24Depart20:5022:03Delay+1h
  5. Pano AkilCrossedArrive21:3022:50Depart21:3523:00Delay+1h 21m
  6. GhotkiCrossedArrive21:5823:23Depart22:0023:29Delay+1h 25m
  7. SadiqabadCrossedArrive23:1600:58Depart23:1801:02Delay+1h 43m
  8. Rahim Yar KhanCrossedArrive23:5001:23Depart23:5201:31Delay+1h 34m
  9. Khanpur Jn.CrossedArrive00:53 +1d02:14Depart00:55 +1d02:18Delay+1h 21m
  10. Samasata JnCrossedArrive02:16 +1d03:40Depart02:18 +1d03:40Delay+1h 24m
  11. BahawalpurCrossedArrive02:30 +1d03:54Depart02:33 +1d03:59Delay+1h 25m
  12. Lodhran JnCrossedArrive02:54 +1d04:13Depart02:56 +1d04:16Delay+1h 19m
  13. Multan CanttCrossedArrive04:00 +1d05:15Depart04:20 +1d05:43Delay+1h 16m
  14. Khanewal JnCrossedArrive05:00 +1d06:26Depart05:05 +1d06:34Delay+1h 26m
  15. Mian ChannuCrossedArrive05:38 +1d07:07Depart05:40 +1d07:09Delay+1h 30m
  16. ChichawatniCrossedArrive06:07 +1d07:33Depart06:09 +1d07:36Delay+1h 27m
  17. SahiwalCrossedArrive06:48 +1d08:04Depart06:50 +1d08:08Delay+1h 17m
  18. OkaraCrossedArrive07:18 +1d08:39Depart07:20 +1d08:42Delay+1h 21m
  19. PattokiCrossedArrive07:52 +1d09:14Depart07:54 +1d09:18Delay+1h 23m
  20. Raiwind Jn.CrossedArrive08:25 +1d09:50Depart08:30 +1d09:53Delay+1h 25m
  21. Kot LakhpatCrossedArrive08:58 +1d10:22Depart09:00 +1d10:25Delay+1h 25m
  22. Lahore CanttCrossedArrive09:20 +1d10:35Depart09:22 +1d10:41Delay+1h 15m
  23. Lahore Jn.CrossedArrive09:40 +1d10:51Depart10:15 +1d11:36Delay+1h 12m
  24. GujranwalaCrossedArrive11:24 +1d12:56Depart11:26 +1d13:08Delay+1h 33m
  25. Wazirabad JnCrossedArrive12:05 +1d13:39Depart12:07 +1d13:45Delay+1h 34m
  26. GujratCrossedArrive12:25 +1d13:58Depart12:27 +1d14:01Delay+1h 34m
  27. Lala Musa Jn.CrossedArrive12:45 +1d14:32Depart12:47 +1d14:40Delay+1h 48m
  28. Kharian CanttCrossedArrive13:01 +1d14:53Depart13:03 +1d15:03Delay+1h 52m
  29. JhelumCrossedArrive13:26 +1d15:31Depart13:28 +1d15:37Delay+2h 06m
  30. Gujar KhanCrossedArrive14:55 +1d16:48Depart14:57 +1d17:00Delay+1h 53m
  31. RawalpindiCrossedArrive16:00 +1d18:17Depart16:25 +1d18:46Delay+2h 17m
  32. Attock City JnCrossedArrive17:49 +1d20:49Depart17:51 +1d20:52Delay+3h 01m
  33. Jahangira RoadCrossedArrive18:27 +1d21:29Depart18:29 +1d21:34Delay+3h 02m
  34. Nowshera JnCrossedArrive18:45 +1d21:49Depart18:47 +1d21:53Delay+3h 05m
  1. Peshawar CityCrossedArrive19:27 +1d22:46Depart19:28 +1d22:52Delay+3h 20m
  2. Peshawar CanttCrossedArrive19:35 +1d23:00Depart—23:28Delay+3h 26m

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.

3,832 GPS positions recorded between 22 Aug 20:59 and 23 Aug 23:28 PKT · 34 of 36 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 2 of 35 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, 12 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.