latetrains.pkLate, on record43 live
Trains/Pakistan Express 46DN/21 August 2026

Pakistan Express 46DN — the run of 21 August 2026

The recorded journey of the run that departed Friday 21 August 2026.
RouteRawalpindi → Karachi Cantt
First recordedGujar Khan, 07:46+59 min — names where it was first seen, not necessarily its origin
At Karachi Canttthe record stops before Karachi Cantt — last recorded at Drigh Road

The record stops before Karachi Cantt — last recorded at Drigh Road at 11:46.

Every recorded crossing

this run only
Show the 29 earlier stops
  1. RawalpindiNo recordArrive—Depart06:00Delay—
  2. Gujar KhanCrossedArrive06:4807:46Depart06:5007:49Delay+59 min
  3. DinaCrossedArrive07:4108:53Depart07:4308:57Delay+1h 13m
  4. JhelumCrossedArrive08:0009:21Depart08:0209:26Delay+1h 22m
  5. Lala Musa Jn.CrossedArrive08:5210:26Depart08:5410:31Delay+1h 35m
  6. GujratCrossedArrive09:2010:51Depart09:2210:55Delay+1h 31m
  7. Wazirabad JnCrossedArrive09:4511:13Depart09:5011:19Delay+1h 28m
  8. Alipur ChathaCrossedArrive10:3512:02Depart10:3712:08Delay+1h 27m
  9. HafizabadCrossedArrive11:0012:35Depart11:0512:41Delay+1h 35m
  10. SukhekeNo recordArrive11:41Depart11:43Delay—
  11. Sangla HillCrossedArrive12:0713:41Depart12:0913:48Delay+1h 35m
  12. Chak Jhumra JnCrossedArrive12:3414:12Depart12:3614:14Delay+1h 39m
  13. FaisalabadCrossedArrive13:0014:36Depart13:3015:35Delay+1h 36m
  14. GojraCrossedArrive14:0916:20Depart14:1116:23Delay+2h 12m
  15. Toba Tek SinghCrossedArrive14:3816:55Depart14:4017:00Delay+2h 17m
  16. Shorkot Cantt JnCrossedArrive15:2017:23Depart15:2517:29Delay+2h 04m
  17. Abdul HakimCrossedArrive15:5017:52Depart15:5217:55Delay+2h 02m
  18. Khanewal JnCrossedArrive16:3018:23Depart16:3518:30Delay+1h 53m
  19. Multan CanttCrossedArrive17:1019:08Depart17:3519:37Delay+1h 58m
  20. Lodhran JnCrossedArrive18:3620:44Depart18:3820:48Delay+2h 09m
  21. BahawalpurCrossedArrive18:50Depart18:5521:10Delay+2h 14m
  22. Khanpur Jn.CrossedArrive20:3522:54Depart20:4023:04Delay+2h 15m
  23. Rahim Yar KhanCrossedArrive21:1223:46Depart21:1423:52Delay+2h 35m
  24. SadiqabadCrossedArrive21:3400:14Depart21:3600:18Delay+2h 41m
  25. GhotkiCrossedArrive22:5401:58Depart22:5602:03Delay+3h 05m
  26. Rohri Jn.CrossedArrive00:10 +1d02:58Depart00:35 +1d03:31Delay+2h 48m
  27. PadidanCrossedArrive02:03 +1d05:13Depart02:05 +1d05:17Delay+3h 10m
  28. Tando AdamCrossedArrive04:38 +1d07:23Depart04:40 +1d07:29Delay+2h 46m
  29. Hyderabad JnCrossedArrive05:35 +1d08:34Depart05:40 +1d09:00Delay+3h
  1. Landhi Jn.CrossedArrive07:42 +1d11:27Depart07:44 +1d11:32Delay+3h 46m
  2. Drigh RoadCrossedArrive08:18 +1d11:46Depart08:20 +1d11:51Delay+3h 28m
  3. Karachi CanttNo recordArrive08:45 +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.

5,332 GPS positions recorded between 21 Aug 06:22 and 22 Aug 12:05 PKT · 28 of 32 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 31 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, 28 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.