Gujar Khan to Rawalpindi
Subak Raftar 101UP — within 15 minutes of the scheduled time 34% of the time, typically 27 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 Gujar Khan to Rawalpindi it typically adds 8 min, from 28 recorded runs. At Rawalpindi it has typically arrived 70 minutes late, from 34 recorded runs.
Every train, compared
6 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Gujar Khan and Rawalpindi 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 Gujar Khan — no booked arrival at Gujar 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 |
|---|---|---|---|---|---|---|---|
| 101Subak Raftar 101UP | 11:00 | 11:55 | 55 min | 54 km | +27 min | 34% | adds 8 min · 28 |
| 13Awam Express 13UP | 12:07 +1d | 13:20 +1d | 1h 13m | 53 km | +1h 42m | 6% | no change · 35 |
| 11Hazara Express 11UP | 12:31 +1d | 13:35 +1d | 1h 04m | 53 km | +45 min | 27% | adds 20 min · 20 |
| 39Jaffar Express 39UP | 14:57 +1d | 16:00 +1d | 1h 03m | not measured yet | +1h 55m | 0% | adds 9 min · 35 |
| 45Pakistan Express 45UP | 16:14 +1d | 17:35 +1d | 1h 21m | 54 km | +2h 25m | 2% | makes up 7 min · 13 |
| 7Tezgam 7UP | 18:50 +1d | 20:00 +1d | 1h 10m | 54 km | +1h 59m | 5% | makes up 4 min · 28 |
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.
- Subak Raftar 101UP101سبک رفتار101اپ11:00→11:5555 min34% on time · +27 minadds 8 min over this leg · 28 runs
- Awam Express 13UP13عوام ایکسپریس 13 اپ12:07 +1d→13:20 +1d1h 13m6% on time · +1h 42mno change over this leg · 35 runs
- Hazara Express 11UP11ہزارا ایکسپریس 11 اپ12:31 +1d→13:35 +1d1h 04m27% on time · +45 minadds 20 min over this leg · 20 runs
- Jaffar Express 39UP39جعفر ایکسپریس 39 اپ14:57 +1d→16:00 +1d1h 03m0% on time · +1h 55madds 9 min over this leg · 35 runs
- Pakistan Express 45UP45پاکستان ایکسپریس 45 اپ16:14 +1d→17:35 +1d1h 21m2% on time · +2h 25mmakes up 7 min over this leg · 13 runs
- Tezgam 7UP7تيزگام 7 اپ18:50 +1d→20:00 +1d1h 10m5% on time · +1h 59mmakes up 4 min over this leg · 28 runs
Travelling the other way? Rawalpindi to Gujar Khan trains →
Common questions
How many trains run from Gujar Khan to Rawalpindi?
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 Gujar Khan to Rawalpindi?
Subak Raftar 101UP, booked at 55 min for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Gujar Khan to Rawalpindi is most likely to be on time?
Subak Raftar 101UP has the best recorded punctuality of the services we hold enough history for: 34% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 27 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 Gujar Khan to Rawalpindi?
Not on the current timetable. Every service on this route is booked to arrive on the same day it departs.
Do trains lose time between Gujar Khan and Rawalpindi?
Typically yes. Hazara Express 11UP adds about 20 min to its delay over this leg, measured across 20 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 Gujar Khan to Rawalpindi by train?
It is between 53 and 54 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 5 of the 6 services; the rest of the track on this route has not been traced yet.
Are these Gujar Khan to Rawalpindi 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.