Kohat Express 133UP — the run of 13 August 2026
Reached Kohat Cantt at 19:33 on 13 August 2026, 11 minutes early — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 9 earlier stops
- RawalpindiCrossedArrive—16:02Depart15:30Delayon time
- Golra SharifCrossedArrive15:5016:00Depart15:5316:02Delay+7 min
- TarnoulCrossedArrive16:0116:09Depart16:0316:13Delay+6 min
- Fateh JangCrossedArrive16:3016:38Depart16:3216:42Delay+6 min
- KahalCrossedArrive17:0617:13Depart17:0717:15Delay+6 min
- Basal SharifCrossedArrive17:1517:20Depart17:1717:22Delay+6 min
- Basal JnCrossedArrive17:2817:25Depart17:3017:34Delayon time
- DomelCrossedArrive17:3617:38Depart17:3717:41Delay+2 min
- Jand JnCrossedArrive18:1018:10Depart18:1218:11Delayon time
- Babari BandaCrossedArrive19:2119:16Depart19:2319:17Delayon time
- Kohat CanttCrossedArrive19:4519:33Depart—19:44Delayon time
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.
966 GPS positions recorded between 14:59 and 19:45 PKT · 11 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. 2 gaps 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.