Rahim Yar Khan to Peshawar Cantt
Rehman Baba Express 47UP — within 15 minutes of the scheduled time 10% of the time, typically 103 minutes late, over 11 days of recorded runs across every stop of its full journey, not this segment alone. That is its whole-journey record, a different promise from this leg alone: over just Rahim Yar Khan to Peshawar Cantt it typically adds 2h 58m, from 32 recorded runs. At Peshawar Cantt it has typically arrived 292 minutes late, from 35 recorded runs.
Every train, compared
4 of 4 with 7+ daysOver this leg is the CHANGE in a train's delay between Rahim Yar Khan and Peshawar Cantt on the same run — not how late it arrives; a train can run late through its whole journey and still show no change here. — means either too few recorded runs on this leg, or — permanently, for a train whose journey starts right here at Rahim Yar Khan — no booked arrival at Rahim Yar Khan to measure from at all. Figures cover runs recorded between 30 July 2026 and 6 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 1Khyber Mail 1UP | 08:44 +1d | 05:15 +2d | 20h 31m | 1,091 km | +1h 39m | 9% | no data |
| 13Awam Express 13UP | 20:33 | 17:30 +1d | 20h 57m | 1,096 km | +1h 42m | 6% | adds 1h 41m · 32 |
| 47Rehman Baba Express 47UP | 23:25 | 18:05 +1d | 18h 40m | 1,432 km | +1h 43m | 10% | adds 2h 58m · 32 |
| 39Jaffar Express 39UP | 23:52 | 19:35 +1d | 19h 43m | not measured yet | +1h 55m | 0% | adds 2h 37m · 17 |
What the marks mean
- Departs · Arrives — scheduled local times, published Pakistan Railways timetable
- +1d — a stop on a later day of the train's own run, not a date
- Typical delay · On-time — the train's whole journey, not this segment alone; typical is the median of its recorded stop arrivals, and on-time is within 15 minutes of the scheduled time
- — — fewer than 7 days of recorded runs for that train
- Over this leg — the change in each train's delay between the two stations above, counted on runs recorded at both (a run whose two stations were logged a day apart is matched too, when that day-shifted leg length matches the train's usual one). “adds” means the train picked up extra delay over this stretch; “makes up” means it arrived less late than it left; “no change” means neither. The figure shown is the middle (median) run: no more than half of a train's counted runs did WORSE than it, and no more than half did better — never a claim that exactly half did either, which isn't always possible to state.
- A large “makes up” usually says more about the leg than the train: where several services on this page all recover time, the stretch is booked with room in it. It never means the train ran early — only that it was less late arriving than departing.
- — — in that column: fewer than 7 runs recorded at both stations on the leg's usual booked times, or — permanently, for a train whose journey starts at this page's origin station — no booked arrival there to measure from at all, which will not fill in with more archive age.
Every service in detail
Typical delay and on-time share are the train's whole journey, from 7+ days of recorded runs. Over this leg is the change in that train's delay between the two stations, from runs recorded at both.
- Khyber Mail 1UP1خیبر میل 1 اپ08:44 +1d→05:15 +2d20h 31m9% on time · +1h 39mno data over this leg
- Awam Express 13UP13عوام ایکسپریس 13 اپ20:33→17:30 +1d20h 57m6% on time · +1h 42madds 1h 41m over this leg · 32 runs
- Rehman Baba Express 47UP47رحمان بابا ایکسپریس47اپ23:25→18:05 +1d18h 40m10% on time · +1h 43madds 2h 58m over this leg · 32 runs
- Jaffar Express 39UP39جعفر ایکسپریس 39 اپ23:52→19:35 +1d19h 43m0% on time · +1h 55madds 2h 37m over this leg · 17 runs
Travelling the other way? Peshawar Cantt to Rahim Yar Khan trains →
Common questions
How many trains run from Rahim Yar Khan to Peshawar Cantt?
4 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Rahim Yar Khan to Peshawar Cantt?
Rehman Baba Express 47UP, booked at 18h 40m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Rahim Yar Khan to Peshawar Cantt is most likely to be on time?
Rehman Baba Express 47UP has the best recorded punctuality of the services we hold enough history for: 10% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 1h 43m. That is its record across every stop of its full journey, not this leg alone: over just Rahim Yar Khan to Peshawar Cantt it typically adds 2h 58m, from 32 recorded runs. Measured from recorded runs, not from the timetable. 4 of 4 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Rahim Yar Khan to Peshawar Cantt?
Yes. All 4 scheduled services are booked to arrive on a later day than they depart: Khyber Mail 1UP, Awam Express 13UP, Rehman Baba Express 47UP, Jaffar Express 39UP.
Do trains lose time between Rahim Yar Khan and Peshawar Cantt?
Typically yes. Rehman Baba Express 47UP adds about 2h 58m to its delay over this leg, measured across 32 recorded runs. That is the CHANGE over the leg, not how late the train arrives: a train can run late its whole journey and add nothing here.
How far is it from Rahim Yar Khan to Peshawar Cantt by train?
It is between 1,091 and 1,432 km along the track, depending on the service. Measured by summing our own GPS traces of trains running the route, not the straight-line distance between the two stations, which is always shorter than the rails. That is measured on 3 of the 4 services; the rest of the track on this route has not been traced yet.
Are these Rahim Yar Khan to Peshawar Cantt timings the real arrival times?
No. The departure and arrival columns are what the published timetable books. The delay columns beside them are what we recorded actually happening, from the operator's own reports and from GPS traces of the trains. Where a delay figure is blank we do not yet hold enough recorded runs to publish one.