Bahauddin Zikria Express 25UP — the run of 23 August 2026
The recorded journey of the run that departed Sunday 23 August 2026.
RouteKarachi City → Multan Cantt
First recordedKarachi Cantt, 19:19+40 min — names where it was first seen, not necessarily its origin
At Multan Canttthe record stops before Multan Cantt — last recorded at Shujabad
The record stops before Multan Cantt — last recorded at Shujabad at 12:39.
Every recorded crossing
this run onlyShow the 23 earlier stops
- Karachi CityNo recordArrive—Depart18:30Delay—
- Karachi CanttCrossedArrive18:4019:19Depart18:5019:34Delay+40 min
- Drigh RoadCrossedArrive19:1019:49Depart19:1219:51Delay+40 min
- Landhi Jn.CrossedArrive19:3220:07Depart19:3420:12Delay+36 min
- Kotri JnCrossedArrive21:2122:43Depart21:2322:48Delay+1h 22m
- Hyderabad JnCrossedArrive21:4523:05Depart22:0023:12Delay+1h 20m
- Tando AdamCrossedArrive22:5200:19Depart22:5400:33Delay+1h 27m
- ShahdadpurCrossedArrive23:1100:54Depart23:1300:56Delay+1h 44m
- Nawabshah Jn.CrossedArrive23:4301:37Depart23:4601:44Delay+1h 54m
- DaurCrossedArrive00:08 +1d02:15Depart00:10 +1d02:16Delay+2h 07m
- MehrabpurCrossedArrive00:58 +1d03:28Depart01:00 +1d03:31Delay+2h 30m
- Rohri Jn.CrossedArrive02:40 +1d04:53Depart03:05 +1d05:19Delay+2h 14m
- GhotkiCrossedArrive03:46 +1d06:30Depart03:48 +1d06:34Delay+2h 44m
- SadiqabadCrossedArrive04:52 +1d08:05Depart04:54 +1d08:10Delay+3h 14m
- Rahim Yar KhanCrossedArrive05:24 +1d08:31Depart05:26 +1d08:36Delay+3h 08m
- Khanpur Jn.CrossedArrive06:15 +1d09:21Depart06:20 +1d09:30Delay+3h 07m
- LiaquatpurCrossedArrive06:51 +1d10:02Depart06:53 +1d10:05Delay+3h 12m
- Dera Nawab SahibCrossedArrive07:22 +1d10:38Depart07:44 +1d10:45Delay+3h 17m
- MubarakpurCrossedArrive07:59 +1d10:58Depart08:01 +1d11:00Delay+3h
- Samasata JnCrossedArrive08:25 +1d11:18Depart08:27 +1d11:20Delay+2h 53m
- BahawalpurCrossedArrive08:41 +1d11:32Depart08:45 +1d11:35Delay+2h 51m
- Lodhran JnCrossedArrive09:08 +1d11:51Depart09:10 +1d11:53Delay+2h 43m
- GilawalaCrossedArrive09:31 +1d12:13Depart09:33 +1d12:14Delay+2h 42m
- Zarif ShahidCrossedArrive09:45 +1d12:25Depart09:47 +1d12:26Delay+2h 41m
- ShujabadCrossedArrive10:00 +1d12:39Depart10:02 +1d12:41Delay+2h 39m
- Multan CanttNo recordArrive10:35 +1dDepart—Delay—
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.
2,069 GPS positions recorded between 23 Aug 19:10 and 24 Aug 13:08 PKT · 24 of 26 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 0 of 25 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. 3 gaps on this run, 39 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.