Sargodha Shuttle-S2dn 278 DN — the run of 2 August 2026
The recorded journey of the run that departed Sunday 2 August 2026.
RouteLala Musa Jn. → Sargodha Jn
First recordedAkhter Karana, 06:16+5 min — names where it was first seen, not necessarily its origin
At Sargodha Jnthe record stops before Sargodha Jn — last recorded at Bhalwal
The record stops before Sargodha Jn — last recorded at Bhalwal at 09:37.
Every recorded crossing
this run onlyShow the 12 earlier stops
- Lala Musa Jn.No recordArrive—Depart06:00Delay—
- Akhter KaranaCrossedArrive06:1206:16Depart06:1406:17Delay+5 min
- Jaurah KaranaCrossedArrive06:3106:22Depart06:3306:33Delayon time
- DingaCrossedArrive06:4506:48Depart06:4706:50Delay+4 min
- Chilian WalaCrossedArrive06:5907:03Depart07:0007:05Delay+4 min
- Mandi BahauddinCrossedArrive07:1107:20Depart07:1307:23Delay+10 min
- HariahCrossedArrive07:2807:40Depart07:3007:44Delay+13 min
- Malakwal JnCrossedArrive07:4507:55Depart07:5508:07Delay+10 min
- Banna Mian WalaNo recordArrive08:04Depart08:05Delay—
- Pind MukkuNo recordArrive08:16Depart08:17Delay—
- MonaCrossedArrive08:2208:36Depart08:2308:40Delay+15 min
- Ratto KalaCrossedArrive08:2908:41Depart08:3008:43Delay+13 min
- PhularwanCrossedArrive08:3808:49Depart08:3909:18Delay+11 min
- BhalwalCrossedArrive09:0009:37Depart09:0209:55Delay+37 min
- Sargodha JnNo recordArrive10:10Depart10:10Delay—
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.
1,324 GPS positions recorded between 06:04 and 10:27 PKT · 11 of 15 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 2 of 14 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, 9 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.