latetrains.pkLate, on record45 live
Trains/Jand Passenger 204dn/5 September 2026

Jand Passenger 204dn — the run of 5 September 2026

The recorded journey of the run that departed Saturday 5 September 2026.
RouteAttock City Jn → Jand Jn
First recordedBasal Jn, 11:52+2 min — names where it was first seen, not necessarily its origin
At Jand Jn12:31on time

Reached Jand Jn at 12:31 on 5 September 2026, 9 minutes early — from the operator's recorded crossing.

Every recorded crossing

this run only
Show the 7 earlier stops
  1. Attock City JnNo recordArrive—Depart11:00Delay—
  2. JhalarNo recordArrive11:28Depart11:29Delay—
  3. SulaimanbadNo recordArrive11:36Depart11:37Delay—
  4. Basal JnCrossedArrive11:5011:52Depart11:5111:54Delay+2 min
  5. DomelCrossedArrive12:0011:59Depart12:0112:01Delayon time
  6. NammalNo recordArrive12:12Depart12:13Delay—
  7. Chur SharifNo recordArrive12:19Depart12:20Delay—
  1. LangarCrossedArrive12:3012:24Depart12:3112:25Delayon time
  2. Jand JnCrossedArrive12:4012:31Depart—12:57Delayon time

Recorded times come from Pakistan Railways’ control room or from the train’s GPS.

The shape of the run

from the GPS trail

Where 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.

268 GPS positions recorded between 11:05 and 12:58 PKT · 4 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, 16 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.