latetrains.pkLate, on record41 live

Bahauddin Zikria Express 26DN — the run of 22 August 2026

The recorded journey of the run that departed Saturday 22 August 2026.
RouteMultan Cantt → Karachi City
First recordedShujabad, 17:12+43 min — names where it was first seen, not necessarily its origin
At Karachi Citythe record stops before Karachi City — last recorded at Karachi Cantt

The record stops before Karachi City — last recorded at Karachi Cantt at 10:31.

Every recorded crossing

this run only
Show the 23 earlier stops
  1. Multan CanttNo recordArrive—Depart16:00Delay—
  2. ShujabadCrossedArrive16:3017:12Depart16:3217:15Delay+43 min
  3. Zarif ShahidCrossedArrive16:4517:26Depart16:4717:29Delay+42 min
  4. GilawalaCrossedArrive17:0017:39Depart17:0217:41Delay+40 min
  5. Lodhran JnCrossedArrive17:2518:01Depart17:2718:04Delay+37 min
  6. BahawalpurCrossedArrive17:4518:21Depart17:5018:29Delay+37 min
  7. Samasata JnNo recordArrive18:04Depart18:06Delay—
  8. MubarakpurCrossedArrive18:2619:07Depart18:2819:10Delay+42 min
  9. Dera Nawab SahibCrossedArrive18:4319:24Depart18:4519:28Delay+42 min
  10. LiaquatpurCrossedArrive19:1519:58Depart19:1720:01Delay+44 min
  11. Khanpur Jn.CrossedArrive20:0020:35Depart20:0520:46Delay+36 min
  12. Rahim Yar KhanCrossedArrive20:3721:31Depart20:3921:36Delay+55 min
  13. SadiqabadCrossedArrive21:0022:03Depart21:0222:06Delay+1h 03m
  14. GhotkiCrossedArrive22:2123:28Depart22:2323:35Delay+1h 07m
  15. Rohri Jn.CrossedArrive23:3500:31Depart00:01 +1d01:02Delay+57 min
  16. MehrabpurCrossedArrive01:00 +1d02:24Depart01:02 +1d02:27Delay+1h 24m
  17. DaurCrossedArrive02:10 +1d03:43Depart02:12 +1d03:46Delay+1h 34m
  18. Nawabshah Jn.CrossedArrive02:54 +1d04:13Depart02:56 +1d04:17Delay+1h 20m
  19. ShahdadpurCrossedArrive03:47 +1d04:55Depart03:49 +1d05:00Delay+1h 08m
  20. Tando AdamCrossedArrive04:22 +1d05:23Depart04:24 +1d05:28Delay+1h 02m
  21. Hyderabad JnCrossedArrive05:10 +1d06:26Depart05:20 +1d06:47Delay+1h 17m
  22. Kotri JnCrossedArrive05:38 +1d07:02Depart05:40 +1d07:06Delay+1h 25m
  23. Landhi Jn.CrossedArrive07:22 +1d09:36Depart07:24 +1d09:41Delay+2h 14m
  1. Drigh RoadCrossedArrive08:02 +1d10:06Depart08:04 +1d10:10Delay+2h 04m
  2. Karachi CanttCrossedArrive08:30 +1d10:31Depart08:45 +1d10:45Delay+2h 01m
  3. Karachi CityNo recordArrive08:55 +1dDepart—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.

2,073 GPS positions recorded between 22 Aug 16:41 and 23 Aug 10:46 PKT · 23 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. 5 gaps on this run, 44 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.