latetrains.pkLate, on record41 live
Trains/Mehr Express 128DN/15 August 2026

Mehr Express 128DN — the run of 15 August 2026

The recorded journey of the run that departed Saturday 15 August 2026.
RouteRawalpindi → Multan Cantt
First recordedGolra Sharif, 16:45+4 min — names where it was first seen, not necessarily its origin
At Multan Cantt08:58+1h 24m

Reached Multan Cantt at 08:58 on 16 August 2026, 84 minutes late — from the operator's recorded crossing.

Every recorded crossing

this run only
Show the 35 earlier stops
  1. RawalpindiCrossedArrive—Depart16:15Delay—
  2. Golra SharifCrossedArrive16:3516:45Depart16:3816:43Delay+4 min
  3. TarnoulCrossedArrive16:4816:49Depart16:5016:53Delayon time
  4. Fateh JangCrossedArrive17:1717:18Depart17:1917:22Delayon time
  5. Basal SharifCrossedArrive18:0518:02Depart18:0618:04Delayon time
  6. Basal JnCrossedArrive18:1518:10Depart18:1718:20Delayon time
  7. DomelCrossedArrive18:2218:25Depart18:2318:30Delay+3 min
  8. NammalCrossedArrive18:3518:44Depart18:45Delayon time
  9. Jand JnCrossedArrive19:0518:58Depart19:0719:08Delayon time
  10. JhammatCrossedArrive19:32Depart19:34Delay+19 min
  11. ChhabCrossedArrive19:4320:04Depart19:4520:06Delay+20 min
  12. InjraCrossedArrive20:00Depart20:02Delay+40 min
  13. Mukhad RoadCrossedArrive20:1520:55Depart20:1720:58Delay+39 min
  14. Daud Khel JnCrossedArrive21:1021:54Depart21:1522:04Delay+40 min
  15. Pai KhelCrossedArrive21:4122:20Depart21:4322:25Delay+39 min
  16. Mian WaliCrossedArrive22:2522:57Depart22:3023:03Delay+28 min
  17. Kundian JnCrossedArrive23:0523:31Depart23:2523:51Delay+6 min
  18. AlluwaliCrossedArrive23:5000:19Depart00:0000:33Delay+24h 03m
  19. PiplanCrossedArrive00:17 +1d00:55Depart00:19 +1d00:55Delay+37 min
  20. Kalur KotCrossedArrive00:50 +1d01:33Depart00:52 +1d01:36Delay+41 min
  21. Darya KhanCrossedArrive01:55 +1d02:59Depart01:57 +1d02:56Delay+1h 02m
  22. BhakkarCrossedArrive02:26 +1d03:20Depart02:28 +1d03:27Delay+55 min
  23. BehalCrossedArrive02:58 +1d03:59Depart03:00 +1d04:03Delay+59 min
  24. Karor Lal EsanCrossedArrive03:20 +1d04:27Depart03:22 +1d04:30Delay+1h 05m
  25. LayyahCrossedArrive03:50 +1d05:02Depart03:55 +1d05:07Delay+1h 08m
  26. Jaman ShahCrossedArrive04:07 +1d05:20Depart04:09 +1d05:23Delay+1h 14m
  27. Kot SultanCrossedArrive04:22 +1d05:38Depart04:24 +1d05:41Delay+1h 15m
  28. Ahsan Pur AhpCrossedArrive04:40 +1d05:55Depart04:42 +1d05:58Delay+1h 14m
  29. Dera DinpanahCrossedArrive04:53 +1d06:12Depart04:55 +1dDelay+1h 18m
  30. Kot AdduCrossedArrive05:05 +1d06:20Depart05:15 +1d06:37Delay+1h 16m
  31. SanawanCrossedArrive05:37 +1d06:55Depart05:39 +1d06:59Delay+1h 16m
  32. GurmaniCrossedArrive05:53 +1d07:08Depart05:55 +1d07:11Delay+1h 14m
  33. Mehmood KotCrossedArrive06:10 +1d07:20Depart06:12 +1d07:26Delay+1h 11m
  34. BudhCrossedArrive06:29 +1d07:43Depart06:30 +1d07:52Delay+1h 21m
  35. MuzaffargarhCrossedArrive06:58 +1d08:10Depart07:08 +1d08:14Delay+1h 02m
  1. Sher Shah JnCrossedArrive07:22 +1d08:39Depart07:24 +1d08:40Delay+1h 17m
  2. Multan CanttCrossedArrive07:35 +1d08:58Depart— +1d09:03Delay+1h 24m

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,196 GPS positions recorded between 15 Aug 15:15 and 16 Aug 09:03 PKT · 34 of 37 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 36 stop-to-stop segments measured straight-line.

How late it was running — each step is a station

1 reading beyond 12 h withheld — no second record on this run supports it.

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. 10 gaps on this run, 112 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.