Rehman Baba Express 47UP — the run of 22 August 2026
The recorded journey of the run that departed Saturday 22 August 2026.
RouteKarachi Cantt → Peshawar Cantt
First recordedDrigh Road, 12:33+14 min — names where it was first seen, not necessarily its origin
At Peshawar Cantt23:29+5h 25m
Reached Peshawar Cantt at 23:29 on 23 August 2026, 325 minutes late — from the operator's recorded crossing.
Every recorded crossing
this run onlyShow the 30 earlier stops
- Karachi CanttNo recordArrive—Depart12:00Delay—
- Drigh RoadCrossedArrive12:2012:33Depart12:2212:37Delay+14 min
- Landhi Jn.CrossedArrive12:4013:06Depart12:4213:10Delay+27 min
- Hyderabad JnCrossedArrive14:5015:41Depart14:5515:51Delay+52 min
- Tando AdamCrossedArrive15:5416:50Depart15:5616:53Delay+57 min
- Nawabshah Jn.CrossedArrive16:3717:52Depart16:3917:55Delay+1h 16m
- DaurNo recordArrive16:57Depart16:59Delay—
- BandhiCrossedArrive17:0618:42Depart17:0818:44Delay+1h 36m
- Bhiria RoadCrossedArrive17:3519:20Depart17:3719:24Delay+1h 45m
- MehrabpurCrossedArrive18:1019:49Depart18:1219:52Delay+1h 39m
- Rohri Jn.CrossedArrive20:1521:22Depart20:4022:15Delay+1h 07m
- Pano AkilCrossedArrive21:0623:16Depart21:0823:19Delay+2h 10m
- GhotkiCrossedArrive21:2823:42Depart21:3000:12Delay+2h 14m
- Mirpur MatheloCrossedArrive21:4300:36Depart21:4500:39Delay+2h 53m
- Rahim Yar KhanCrossedArrive23:2301:52Depart23:2501:59Delay+2h 29m
- Samasata JnCrossedArrive01:42 +1d04:29Depart01:44 +1d04:30Delay+2h 47m
- BahawalpurCrossedArrive01:55 +1d04:43Depart02:00 +1d04:48Delay+2h 49m
- Multan CanttCrossedArrive03:20 +1d06:01Depart03:40 +1d06:30Delay+2h 41m
- Khanewal JnCrossedArrive04:21 +1d07:14Depart04:23 +1d07:17Delay+2h 54m
- Toba Tek SinghCrossedArrive05:40 +1d08:37Depart05:42 +1d08:41Delay+2h 58m
- FaisalabadCrossedArrive06:55 +1d10:02Depart07:25 +1d10:39Delay+3h 08m
- Sangla HillCrossedArrive08:06 +1d11:30Depart08:08 +1d11:34Delay+3h 24m
- HafizabadCrossedArrive09:10 +1d12:29Depart09:12 +1d13:14Delay+3h 20m
- Alipur ChathaCrossedArrive09:36 +1d13:41Depart09:38 +1d13:44Delay+4h 06m
- Wazirabad JnCrossedArrive10:41 +1d14:24Depart10:43 +1d14:46Delay+3h 44m
- Lala Musa Jn.CrossedArrive11:27 +1d15:19Depart11:29 +1d15:24Delay+3h 53m
- RawalpindiCrossedArrive14:25 +1d18:57Depart14:45 +1d19:21Delay+4h 32m
- Attock City JnCrossedArrive16:10 +1d21:13Depart16:14 +1d21:15Delay+5h 04m
- Jahangira RoadCrossedArrive16:51 +1d21:53Depart16:55 +1d21:56Delay+5h 02m
- Nowshera JnCrossedArrive17:12 +1d22:13Depart17:16 +1d22:16Delay+5h 01m
- Peshawar CityCrossedArrive17:54 +1d23:19Depart17:55 +1d23:21Delay+5h 26m
- Peshawar CanttCrossedArrive18:05 +1d23:29Depart18:05 +1d00:09Delay+5h 25m
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,850 GPS positions recorded between 22 Aug 12:16 and 24 Aug 00:10 PKT · 30 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. 13 gaps on this run, 123 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.