Attock Passenger 202dn — the run of 2 September 2026
The recorded journey of the run that departed Wednesday 2 September 2026.
RouteAttock City Jn → Mari Indus
First recordedBasal Jn, 16:51+13 min — names where it was first seen, not necessarily its origin
At Mari Industhe record stops before Mari Indus — last recorded at Masan Railway Station
The record stops before Mari Indus — last recorded at Masan Railway Station at 20:00.
Every recorded crossing
this run onlyShow the 14 earlier stops
- Attock City JnNo recordArrive—Depart15:55Delay—
- JhalarNo recordArrive16:18Depart16:19Delay—
- SulaimanbadNo recordArrive16:26Depart16:27Delay—
- Basal JnCrossedArrive16:3816:51Depart16:4016:57Delay+13 min
- DomelCrossedArrive16:4616:59Depart16:4717:00Delay+13 min
- NammalCrossedArrive16:5717:11Depart16:5817:13Delay+15 min
- Chur SharifNo recordArrive17:05Depart17:06Delay—
- LangarNo recordArrive17:15Depart17:16Delay—
- Jand JnCrossedArrive17:3217:34Depart17:3417:41Delay+3 min
- UchhriNo recordArrive17:52Depart18:02Delay—
- JhammatNo recordArrive18:18Depart18:19Delay—
- ChhabCrossedArrive18:3018:33Depart18:3118:35Delay+3 min
- KhatakbadCrossedArrive18:4718:50Depart18:4818:51Delay+4 min
- InjraNo recordArrive19:05Depart19:06Delay—
- Mukhad RoadCrossedArrive19:2719:27Depart19:2819:29Delayon time
- Masan Railway StationCrossedArrive20:0720:00Depart20:0820:01Delayon time
- Daud Khel JnNo recordArrive20:40Depart20:55Delay—
- Mari IndusNo recordArrive21:15Depart—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.
458 GPS positions recorded between 16:03 and 20:27 PKT · 8 of 18 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 0 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. 6 gaps on this run, 91 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.