Rawalpindi to Khanpur Jn.
Jaffar Express 40DN — within 15 minutes of the scheduled time 26% of the time, typically 54 minutes late, over 10 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 Rawalpindi to Khanpur Jn. it typically adds 28 min, from 33 recorded runs. At Khanpur Jn. it has typically arrived 45 minutes late, from 33 recorded runs.
Every train, compared
6 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Rawalpindi and Khanpur Jn. 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 Rawalpindi — no booked arrival at Rawalpindi to measure from at all. Figures cover runs recorded between 30 July 2026 and 6 October 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 2Khyber Mail 2DN | 01:50 +1d | 17:25 +1d | 15h 35m | 875 km | +2h 02m | 7% | no data |
| 46Pakistan Express 46DN | 06:00 | 20:35 | 14h 35m | 806 km | +1h 02m | 5% | no data |
| 8Tezgam 8DN | 08:00 | 22:10 | 14h 10m | 863 km | +58 min | 17% | no data |
| 40Jaffar Express 40DN | 10:35 | 01:18 +1d | 14h 43m | 872 km | +54 min | 26% | adds 28 min · 33 |
| 14Awam Express 14DN | 12:30 | 04:55 +1d | 16h 25m | 877 km | +2h 09m | 8% | adds 1h 42m · 33 |
| 12Hazara Express 12DN | 17:10 | 10:50 +1d | 17h 40m | 825 km | +1h 17m | 10% | adds 49 min · 23 |
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 2DN2خیبر میل 2 ڈائون01:50 +1d→17:25 +1d15h 35m7% on time · +2h 02mno data over this leg
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون06:00→20:3514h 35m5% on time · +1h 02mno data over this leg
- Tezgam 8DN8تیزگام 8 ڈاؤن08:00→22:1014h 10m17% on time · +58 minno data over this leg
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون10:35→01:18 +1d14h 43m26% on time · +54 minadds 28 min over this leg · 33 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون12:30→04:55 +1d16h 25m8% on time · +2h 09madds 1h 42m over this leg · 33 runs
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن17:10→10:50 +1d17h 40m10% on time · +1h 17madds 49 min over this leg · 23 runs
Travelling the other way? Khanpur Jn. to Rawalpindi trains →
Common questions
How many trains run from Rawalpindi to Khanpur Jn.?
6 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Rawalpindi to Khanpur Jn.?
Tezgam 8DN, booked at 14h 10m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Rawalpindi to Khanpur Jn. is most likely to be on time?
Jaffar Express 40DN has the best recorded punctuality of the services we hold enough history for: 26% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 54 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 6 of 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Rawalpindi to Khanpur Jn.?
Yes. 3 of the 6 scheduled services are booked to arrive on a later day than they depart: Jaffar Express 40DN, Awam Express 14DN, Hazara Express 12DN.
Do trains lose time between Rawalpindi and Khanpur Jn.?
Typically yes. Awam Express 14DN adds about 1h 42m to its delay over this leg, measured across 33 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 Rawalpindi to Khanpur Jn. by train?
It is between 806 and 877 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.
Are these Rawalpindi to Khanpur Jn. 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.