latetrains.pkLate, on record39 live
Trains/Shalimar Express 28DN/15 August 2026

Shalimar Express 28DN — the run of 15 August 2026

The recorded journey of the run that departed Saturday 15 August 2026.
RouteLahore Jn. → Karachi Cantt
First recordedMultan Cantt, 12:08on time — names where it was first seen, not necessarily its origin
At Karachi Cantt04:36+2h 16m

Reached Karachi Cantt at 04:36 on 16 August 2026, 136 minutes late — from the operator's recorded crossing.

Every recorded crossing

this run only
Show the 12 earlier stops
  1. Lahore Jn.CrossedArrive—Depart07:10Delayon time
  2. Sangla HillNo recordArrive08:27Depart08:29Delay—
  3. FaisalabadNo recordArrive09:40Depart09:45Delay—
  4. Toba Tek SinghNo recordArrive10:53Depart10:55Delay—
  5. Multan CanttCrossedArrive12:5012:08Depart13:1013:12Delayon time
  6. BahawalpurCrossedArrive14:2514:19Depart14:2714:27Delayon time
  7. Khanpur Jn.CrossedArrive16:0516:02Depart16:0716:11Delayon time
  8. Rahim Yar KhanCrossedArrive16:3017:00Depart16:3217:10Delay+28 min
  9. GhotkiCrossedArrive17:5018:47Depart17:5218:58Delay+55 min
  10. Rohri Jn.CrossedArrive19:0019:51Depart19:2520:51Delay+27 min
  11. Nawabshah Jn.CrossedArrive21:5823:33Depart22:0023:37Delay+1h 34m
  12. Hyderabad JnCrossedArrive23:4501:29Depart23:5001:41Delay+1h 39m
  1. Landhi Jn.CrossedArrive01:40 +1d03:55Depart01:42 +1d04:00Delay+2h 13m
  2. Karachi CanttCrossedArrive02:20 +1d04:36Depart02:20 +1d06:12Delay+2h 16m

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.

4,584 GPS positions recorded between 15 Aug 06:33 and 16 Aug 06:21 PKT · 10 of 14 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 2 of 13 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. 7 gaps on this run, 83 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.