Chanab Express 136dn — the run of 9 August 2026
Reached Sargodha Jn at 19:51 on 9 August 2026, 7 minutes late — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 16 earlier stops
- Lala Musa Jn.No recordArrive—Depart15:45Delay—
- Akhter KaranaCrossedArrive15:5416:14Depart15:5516:15Delay+20 min
- Jaurah KaranaCrossedArrive16:0216:19Depart16:0316:27Delay+18 min
- DingaCrossedArrive16:1516:42Depart16:1716:44Delay+28 min
- Chak Sher MuhammadCrossedArrive16:2416:56Depart16:2516:58Delay+33 min
- Chilian WalaNo recordArrive16:30Depart16:31Delay—
- Mandi BahauddinCrossedArrive16:4917:12Depart—17:15Delay+23 min
- HariahCrossedArrive17:1317:29Depart17:1417:31Delay+17 min
- Malakwal JnCrossedArrive17:3017:40Depart17:4017:54Delay+11 min
- Banna Mian WalaNo recordArrive17:49Depart17:50Delay—
- Pakhowal (Halt)No recordArrive17:56Depart17:57Delay—
- Pind MukkuNo recordArrive18:02Depart18:03Delay—
- MonaNo recordArrive18:10Depart18:11Delay—
- Ratto KalaCrossedArrive18:1718:30Depart18:1818:32Delay+13 min
- PhularwanCrossedArrive18:2518:39Depart18:2718:41Delay+14 min
- BhalwalCrossedArrive18:4619:01Depart18:4819:13Delay+16 min
- AjnalaCrossedArrive19:0819:26Depart19:0919:28Delay+19 min
- Sargodha JnCrossedArrive19:4519:51Depart19:4520:02Delay+7 min
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.
663 GPS positions recorded between 16:05 and 20:03 PKT · 12 of 18 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 5 of 17 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. 1 gap on this run, 26 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.