Rehman Baba Express 48DN — the run of 21 August 2026
The recorded journey of the run that departed Friday 21 August 2026.
RoutePeshawar Cantt → Karachi Cantt
First recordedPeshawar City, 11:09+1 min — names where it was first seen, not necessarily its origin
At Karachi Cantt22:14+5h 19m
Reached Karachi Cantt at 22:14 on 22 August 2026, 319 minutes late — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 30 earlier stops
- Peshawar CanttNo recordArrive—Depart11:00Delay—
- Peshawar CityCrossedArrive11:0911:09Depart11:1011:21Delay+1 min
- Nowshera JnCrossedArrive11:4011:57Depart11:4211:59Delay+18 min
- Jahangira RoadCrossedArrive12:0112:14Depart12:0512:21Delay+13 min
- Attock City JnCrossedArrive12:4213:05Depart12:4613:09Delay+24 min
- RawalpindiCrossedArrive14:2014:55Depart14:4015:36Delay+36 min
- Lala Musa Jn.CrossedArrive17:1819:05Depart17:2019:17Delay+1h 47m
- Wazirabad JnCrossedArrive18:0420:14Depart18:0620:19Delay+2h 11m
- Alipur ChathaCrossedArrive18:4721:01Depart18:4921:04Delay+2h 14m
- HafizabadCrossedArrive19:1321:36Depart19:1521:41Delay+2h 23m
- Sangla HillCrossedArrive20:11Depart20:1322:37Delay+2h 24m
- FaisalabadCrossedArrive21:1023:16Depart21:4000:01Delay+2h 07m
- Toba Tek SinghCrossedArrive22:4001:36Depart22:4201:40Delay+2h 57m
- Khanewal JnCrossedArrive00:25 +1d02:58Depart00:27 +1d03:03Delay+2h 34m
- Multan CanttCrossedArrive01:05 +1d03:41Depart01:25 +1d04:18Delay+2h 37m
- BahawalpurCrossedArrive02:40 +1d05:23Depart02:45 +1d05:28Delay+2h 44m
- Samasata JnCrossedArrive02:58 +1d05:44Depart03:00 +1d06:08Delay+2h 47m
- Rahim Yar KhanCrossedArrive04:49 +1d08:39Depart04:51 +1d08:44Delay+3h 50m
- Mirpur MatheloCrossedArrive06:00 +1d10:08Depart06:02 +1d10:21Delay+4h 08m
- GhotkiCrossedArrive06:27 +1d10:41Depart06:29 +1d10:49Delay+4h 15m
- Pano AkilCrossedArrive06:53 +1d11:09Depart06:55 +1d11:11Delay+4h 17m
- Rohri Jn.CrossedArrive07:40 +1d11:47Depart08:05 +1d12:50Delay+4h 07m
- MehrabpurCrossedArrive09:13 +1d14:11Depart09:15 +1d14:14Delay+4h 58m
- Bhiria RoadCrossedArrive09:44 +1d14:38Depart09:46 +1d14:40Delay+4h 54m
- BandhiCrossedArrive10:28 +1d15:25Depart10:30 +1d15:28Delay+4h 58m
- DaurNo recordArrive10:43 +1dDepart10:45 +1dDelay—
- Nawabshah Jn.CrossedArrive11:23 +1d16:09Depart11:25 +1d16:15Delay+4h 46m
- Tando AdamCrossedArrive12:48 +1d17:13Depart12:50 +1d17:18Delay+4h 26m
- Hyderabad JnCrossedArrive13:45 +1d18:22Depart13:50 +1d18:32Delay+4h 38m
- Landhi Jn.CrossedArrive15:41 +1d21:30Depart15:43 +1d21:33Delay+5h 49m
- Drigh RoadCrossedArrive16:23 +1d21:51Depart16:25 +1d21:55Delay+5h 29m
- Karachi CanttCrossedArrive16:55 +1d22:14Depart16:55 +1d22:26Delay+5h 19m
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.
3,126 GPS positions recorded between 21 Aug 11:05 and 22 Aug 22:26 PKT · 29 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. 10 gaps on this run, 81 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.