latetrains.pkLate, on record37 live
Trains/Kohat Express 134DN/7 September 2026

Kohat Express 134DN — the run of 7 September 2026

The recorded journey of the run that departed Monday 7 September 2026.
RouteKohat Cantt → Rawalpindi
First recordedBabari Banda, 07:51on time — names where it was first seen, not necessarily its origin
At Rawalpindithe record stops before Rawalpindi — last recorded at Golra Sharif

The record stops before Rawalpindi — last recorded at Golra Sharif at 11:21.

Every recorded crossing

this run only
Show the 8 earlier stops
  1. Kohat CanttNo recordArrive—Depart07:30Delay—
  2. Babari BandaCrossedArrive07:5307:51Depart07:5507:53Delayon time
  3. Jand JnCrossedArrive09:0409:03Depart09:0609:07Delayon time
  4. DomelCrossedArrive09:3009:33Depart09:3109:35Delay+4 min
  5. Basal JnNo recordArrive09:42Depart09:44Delay—
  6. Basal SharifNo recordArrive09:50Depart09:51Delay—
  7. KahalCrossedArrive09:5909:57Depart10:0009:58Delayon time
  8. Fateh JangCrossedArrive10:3410:31Depart10:3610:36Delayon time
  1. TarnoulCrossedArrive11:0311:09Depart11:0511:11Delay+7 min
  2. Golra SharifCrossedArrive11:1411:21Depart11:1711:24Delay+7 min
  3. RawalpindiNo recordArrive11:35Depart—Delay—

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.

1,233 GPS positions recorded between 07:34 and 11:46 PKT · 7 of 11 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 10 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.