Hazara Express 11UP — the run of 15 August 2026
Reached Havelian at 21:30 on 16 August 2026, 291 minutes late — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 52 earlier stops
- Karachi CityCrossedArrive—Depart06:35Delayon time
- Karachi CanttCrossedArrive06:4508:17Depart07:0008:33Delay+1h 18m
- Drigh RoadCrossedArrive07:2208:46Depart07:2408:50Delay+1h 22m
- Landhi Jn.CrossedArrive07:4809:05Depart07:5009:08Delay+1h 15m
- Kotri JnCrossedArrive09:3811:20Depart09:3811:27Delay+1h 42m
- Hyderabad JnCrossedArrive10:0011:49Depart10:1011:58Delay+1h 39m
- Tando AdamCrossedArrive11:0712:56Depart11:0913:02Delay+1h 49m
- ShahdadpurCrossedArrive11:2614:06Depart11:2814:09Delay+2h 38m
- SarhariCrossedArrive11:4414:30Depart11:46Delay+2h 45m
- Nawabshah Jn.CrossedArrive11:5814:47Depart12:0014:54Delay+2h 48m
- PadidanCrossedArrive12:4216:02Depart12:4416:08Delay+3h 19m
- Bhiria RoadCrossedArrive13:0216:19Depart13:0416:28Delay+3h 18m
- MehrabpurCrossedArrive13:3516:54Depart13:3717:02Delay+3h 17m
- GambatCrossedArrive14:1417:30Depart14:1617:34Delay+3h 14m
- KhairpurCrossedArrive14:5018:08Depart14:5218:11Delay+3h 16m
- Rohri Jn.CrossedArrive15:3518:43Depart16:0019:09Delay+2h 43m
- Pano AkilCrossedArrive16:2619:56Depart16:2820:00Delay+3h 29m
- GhotkiCrossedArrive17:0020:20Depart17:0220:25Delay+3h 20m
- Mirpur MatheloCrossedArrive17:3420:47Depart17:3620:52Delay+3h 12m
- DaharkiCrossedArrive17:5821:07Depart18:0021:11Delay+3h 08m
- SadiqabadCrossedArrive18:5221:55Depart18:5422:00Delay+3h 01m
- Rahim Yar KhanCrossedArrive19:3022:27Depart19:3222:32Delay+2h 56m
- Khanpur Jn.CrossedArrive20:2023:15Depart20:2523:23Delay+2h 50m
- LiaquatpurCrossedArrive20:5823:53Depart21:0023:56Delay+2h 53m
- Dera Nawab SahibCrossedArrive21:3500:27Depart21:3700:32Delay+2h 51m
- MubarakpurCrossedArrive21:5200:44Depart21:5400:48Delay+2h 51m
- Samasata JnCrossedArrive22:0601:08Depart22:0801:12Delay+3h
- BahawalpurCrossedArrive22:2201:24Depart22:2701:31Delay+2h 58m
- Lodhran JnCrossedArrive22:5001:46Depart22:5201:49Delay+2h 54m
- GilawalaCrossedArrive23:1302:11Depart23:1502:14Delay+2h 56m
- ShujabadCrossedArrive23:3802:33Depart23:4002:37Delay+2h 53m
- Multan CanttCrossedArrive00:10 +1d03:08Depart00:40 +1d03:37Delay+2h 28m
- Khanewal JnCrossedArrive01:20 +1d04:20Depart01:25 +1d04:30Delay+3h
- Abdul HakimCrossedArrive01:55 +1d05:02Depart01:57 +1d05:05Delay+3h 05m
- Shorkot Cantt JnCrossedArrive02:30 +1d05:32Depart02:35 +1d05:43Delay+2h 57m
- Jhang SadarCrossedArrive04:05 +1d07:08Depart04:10 +1d07:18Delay+2h 59m
- SillanwaliCrossedArrive05:56 +1d08:48Depart05:58 +1d08:51Delay+2h 52m
- Shaheenabad JnCrossedArrive06:12 +1d09:09Depart06:13 +1d09:12Delay+2h 58m
- Sargodha JnCrossedArrive06:35 +1d09:37Depart06:45 +1d10:00Delay+3h 02m
- BhalwalCrossedArrive07:35 +1d10:36Depart07:37 +1d10:40Delay+3h 02m
- PhularwanCrossedArrive07:58 +1d11:00Depart08:00 +1d11:03Delay+3h 03m
- Malakwal JnCrossedArrive08:32 +1d11:32Depart08:37 +1d11:43Delay+3h 01m
- Mandi BahauddinCrossedArrive09:03 +1d12:20Depart09:05 +1d12:22Delay+3h 17m
- DingaCrossedArrive09:30 +1d12:42Depart09:32 +1d12:44Delay+3h 12m
- Lala Musa Jn.CrossedArrive10:05 +1d13:13Depart10:30 +1d13:45Delay+3h 08m
- JhelumCrossedArrive11:12 +1d14:17Depart11:14 +1d14:35Delay+3h 05m
- Gujar KhanCrossedArrive12:29 +1d15:48Depart12:31 +1d15:52Delay+3h 20m
- RawalpindiCrossedArrive13:35 +1d17:25Depart14:05 +1d18:08Delay+3h 51m
- Golra SharifCrossedArrive14:22 +1d18:40Depart14:26 +1dDelay+4h 18m
- Taxila CanttCrossedArrive14:44 +1d19:07Depart14:46 +1d19:10Delay+4h 23m
- Kot Najib UllahCrossedArrive15:18 +1d19:56Depart15:20 +1d19:56Delay+4h 38m
- Haripur HazaraCrossedArrive15:36 +1d20:16Depart15:38 +1d20:22Delay+4h 41m
- BaldherCrossedArrive16:15 +1d21:05Depart16:16 +1d21:08Delay+4h 51m
- HavelianCrossedArrive16:40 +1d21:30Depart16:40 +1d21:31Delay+4h 51m
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.
7,851 GPS positions recorded between 15 Aug 06:32 and 16 Aug 21:40 PKT · 53 of 54 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 1 of 53 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. 11 gaps on this run, 125 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.