Bhullhe Shah passengers 258Dn — the run of 4 September 2026
The record stops before Pakpattan — last recorded at Haveli Wasawewala at 23:13.
Every recorded crossing
this run onlyShow the 8 earlier stops
- Lahore Jn.No recordArrive—Depart16:00Delay—
- Kot LakhpatCrossedArrive16:2816:55Depart16:3016:58Delay+28 min
- Raiwind Jn.CrossedArrive16:5717:31Depart17:0217:31Delay+34 min
- Kasur JnCrossedArrive17:3518:18Depart18:0519:23Delay+43 min
- KhudianNo recordArrive18:34Depart18:36Delay—
- UsmanwalaCrossedArrive18:5020:29Depart18:5220:56Delay+1h 39m
- KanganpurCrossedArrive19:2921:32Depart19:3121:36Delay+2h 03m
- Mandi AhmadabadCrossedArrive19:5822:02Depart20:0022:04Delay+2h 04m
- BasirpurCrossedArrive20:2422:38Depart20:2622:41Delay+2h 14m
- Haveli WasawewalaCrossedArrive20:5023:13Depart20:5223:15Delay+2h 23m
- PakpattanNo recordArrive21:30Depart21:30Delay—
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.
1,396 GPS positions recorded between 4 Sep 16:26 and 5 Sep 00:05 PKT · 8 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, 6 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.