Rawalpindi to Havelian
Hazara Express 11UP — within 15 minutes of the scheduled time 27% of the time, typically 45 minutes late, over 12 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 Havelian it typically adds 36 min, from 12 recorded runs. At Havelian it has typically arrived 195 minutes late, from 16 recorded runs.
Every train, compared
1 of 2 with 7+ daysOver this leg is the CHANGE in a train's delay between Rawalpindi and Havelian 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 31 July 2026 and 4 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 267Rawalpindi Passenger 267UP | 08:00 | 10:50 | 2h 50m | 92 km | — | — | no data |
| 11Hazara Express 11UP | 14:05 +1d | 16:40 +1d | 2h 35m | 91 km | +45 min | 27% | adds 36 min · 12 |
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.
Travelling the other way? Havelian to Rawalpindi trains →
Common questions
How many trains run from Rawalpindi to Havelian?
2 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 Havelian?
Hazara Express 11UP, booked at 2h 35m 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 Havelian is most likely to be on time?
Hazara Express 11UP has the best recorded punctuality of the services we hold enough history for: 27% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 45 min. That is its record across every stop of its full journey, not this leg alone: over just Rawalpindi to Havelian it typically adds 36 min, from 12 recorded runs. Measured from recorded runs, not from the timetable. 1 of 2 services on this route currently has enough recorded history to rank at all.
Is there an overnight train from Rawalpindi to Havelian?
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 Rawalpindi and Havelian?
Typically yes. Hazara Express 11UP adds about 36 min to its delay over this leg, measured across 12 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 Havelian by train?
It is between 91 and 92 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 Havelian 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.