Attock Passenger 201up — the run of 7 September 2026
The recorded journey of the run that departed Monday 7 September 2026.
RouteMari Indus → Attock City Jn
First recordedDaud Khel Jn, 03:16on time — names where it was first seen, not necessarily its origin
At Attock City Jnthe record stops before Attock City Jn — last recorded at Jand Jn
The record stops before Attock City Jn — last recorded at Jand Jn at 06:27.
Every recorded crossing
this run onlyShow the 5 earlier stops
- Mari IndusNo recordArrive—Depart03:00Delay—
- Daud Khel JnCrossedArrive03:2003:16Depart03:3504:02Delayon time
- Masan Railway StationCrossedArrive03:5504:27Depart03:5604:28Delay+33 min
- Mukhad RoadNo recordArrive04:15Depart04:16Delay—
- InjraNo recordArrive04:29Depart04:30Delay—
- KhatakbadCrossedArrive04:4105:29Depart04:4205:30Delay+49 min
- ChhabNo recordArrive04:56Depart04:57Delay—
- JhammatNo recordArrive05:11Depart05:12Delay—
- UchhriNo recordArrive05:29Depart05:30Delay—
- Jand JnCrossedArrive05:5006:27Depart05:5206:30Delay+37 min
7 stops — no report yet
- LangarNo recordArrive06:00Depart06:01Delay—
- Chur SharifNo recordArrive06:08Depart06:09Delay—
- NammalNo recordArrive06:19Depart06:20Delay—
- DomelNo recordArrive06:35Depart06:36Delay—
- Basal JnNo recordArrive06:47Depart06:48Delay—
- SulaimanbadNo recordArrive06:58Depart06:59Delay—
- JhalarNo recordArrive07:11Depart07:12Delay—
- Attock City JnNo recordArrive07:45Depart—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.
814 GPS positions recorded between 03:02 and 06:59 PKT · 4 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. 2 gaps on this run, 78 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.