Bhullhe Shah passengers 258Dn — the run of 5 September 2026
The recorded journey of the run that departed Saturday 5 September 2026.
RouteLahore Jn. → Pakpattan
First recordedKot Lakhpat, 16:39+12 min — names where it was first seen, not necessarily its origin
At Pakpattanthe record stops before Pakpattan — last recorded at Haveli Wasawewala
The record stops before Pakpattan — last recorded at Haveli Wasawewala at 22:27.
Every recorded crossing
this run onlyShow the 8 earlier stops
- Lahore Jn.No recordArrive—Depart16:00Delay—
- Kot LakhpatCrossedArrive16:2816:39Depart16:3016:42Delay+12 min
- Raiwind Jn.No recordArrive16:57Depart17:02Delay—
- Kasur JnCrossedArrive17:3517:59Depart18:0519:02Delay+24 min
- KhudianCrossedArrive18:3419:43Depart18:3619:46Delay+1h 10m
- UsmanwalaCrossedArrive18:5020:03Depart18:5220:22Delay+1h 14m
- KanganpurCrossedArrive19:2920:53Depart19:3120:57Delay+1h 25m
- Mandi AhmadabadCrossedArrive19:5821:19Depart20:0021:23Delay+1h 22m
- BasirpurCrossedArrive20:2421:55Depart20:2621:59Delay+1h 32m
- Haveli WasawewalaCrossedArrive20:5022:27Depart20:5222:31Delay+1h 37m
- 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.
291 GPS positions recorded between 16:17 and 23:28 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. 5 gaps on this run, 52 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.