Jaffar Express 40DN — the run of 23 August 2026
The recorded journey of the run that departed Sunday 23 August 2026.
RoutePeshawar Cantt → Jacobabad Jn
First recordedPeshawar City, 06:09on time — names where it was first seen, not necessarily its origin
At Jacobabad Jnthe record stops before Jacobabad Jn — last recorded at Pano Akil
The record stops before Jacobabad Jn — last recorded at Pano Akil at 05:23.
Every recorded crossing
this run onlyShow the 29 earlier stops
- Peshawar CanttNo recordArrive—Depart07:00Delay—
- Peshawar CityCrossedArrive07:0906:09Depart07:1106:12Delayon time
- Nowshera JnCrossedArrive07:4106:51Depart07:4306:53Delayon time
- Jahangira RoadCrossedArrive08:0007:11Depart08:0207:14Delayon time
- Attock City JnCrossedArrive08:4007:52Depart08:4207:55Delayon time
- RawalpindiCrossedArrive10:1010:17Depart10:3510:59Delay+8 min
- Gujar KhanCrossedArrive11:2712:01Depart11:2912:04Delay+34 min
- JhelumCrossedArrive12:3813:15Depart12:4013:19Delay+37 min
- Kharian CanttCrossedArrive13:0013:46Depart13:0413:49Delay+46 min
- Lala Musa Jn.CrossedArrive13:4014:02Depart13:4214:06Delay+22 min
- GujratCrossedArrive14:1014:25Depart14:1214:55Delay+16 min
- Wazirabad JnNo recordArrive14:28Depart14:30Delay—
- GujranwalaNo recordArrive14:55Depart14:57Delay—
- Lahore Jn.CrossedArrive16:1016:41Depart16:4517:11Delay+32 min
- Lahore CanttCrossedArrive16:5817:19Depart17:0017:27Delay+21 min
- Raiwind Jn.CrossedArrive17:3018:05Depart17:3518:10Delay+36 min
- PattokiCrossedArrive18:0618:41Depart18:0818:45Delay+36 min
- OkaraCrossedArrive18:5019:18Depart18:5219:22Delay+29 min
- SahiwalCrossedArrive19:3719:50Depart19:3919:56Delay+14 min
- ChichawatniCrossedArrive20:1020:26Depart20:1220:31Delay+16 min
- Mian ChannuCrossedArrive20:3820:56Depart20:4020:59Delay+19 min
- Khanewal JnCrossedArrive21:1521:32Depart21:2021:47Delay+17 min
- Multan CanttCrossedArrive21:5522:23Depart22:1522:47Delay+28 min
- Lodhran JnCrossedArrive23:1523:58Depart—00:03Delay+44 min
- BahawalpurCrossedArrive23:3500:18Depart23:3800:22Delay+43 min
- Samasata JnNo recordArrive00:10 +1dDepart00:12 +1dDelay—
- Khanpur Jn.CrossedArrive01:18 +1d01:56Depart01:20 +1d02:14Delay+38 min
- Rahim Yar KhanCrossedArrive01:52 +1d02:58Depart01:54 +1d03:04Delay+1h 06m
- SadiqabadCrossedArrive02:14 +1d03:28Depart02:16 +1d03:33Delay+1h 14m
- GhotkiCrossedArrive03:23 +1d05:00Depart03:25 +1d05:04Delay+1h 37m
- Pano AkilCrossedArrive03:50 +1d05:23Depart03:55 +1d05:37Delay+1h 34m
- Rohri Jn.No recordArrive04:45 +1dDepart05:10 +1dDelay—
- SukkurNo recordArrive05:20 +1dDepart05:25 +1dDelay—
- ShikarpurNo recordArrive06:21 +1dDepart06:23 +1dDelay—
- Jacobabad JnNo recordArrive07:30 +1dDepart07:50 +1dDelay—
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,112 GPS positions recorded between 23 Aug 06:08 and 24 Aug 06:09 PKT · 27 of 35 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 2 of 34 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. 5 gaps on this run, 143 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.