Subak Raftar 101UP — the run of 24 August 2026
The recorded journey of the run that departed Monday 24 August 2026.
RouteLahore Jn. → Rawalpindi
First recordedGujranwala, 08:39+42 min — names where it was first seen, not necessarily its origin
At Rawalpindithe record stops before Rawalpindi — last recorded at Chaklala
The record stops before Rawalpindi — last recorded at Chaklala at 13:05.
Every recorded crossing
this run onlyShow the 6 earlier stops
- Lahore Jn.No recordArrive—Depart07:00Delay—
- GujranwalaCrossedArrive07:5808:39Depart08:0008:45Delay+42 min
- Wazirabad JnCrossedArrive08:2809:10Depart08:3009:13Delay+42 min
- GujratCrossedArrive08:4809:26Depart08:5009:34Delay+38 min
- Lala Musa Jn.CrossedArrive09:1609:55Depart09:1810:01Delay+40 min
- JhelumCrossedArrive09:5010:45Depart09:5210:48Delay+55 min
- Gujar KhanCrossedArrive10:5812:11Depart11:0012:13Delay+1h 14m
- ChaklalaCrossedArrive11:4013:05Depart11:4213:07Delay+1h 25m
- RawalpindiNo recordArrive11:55Depart—Delay—
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.
994 GPS positions recorded between 07:10 and 13:10 PKT · 7 of 9 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 0 of 8 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, 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.