267 Rawalpindi Passenger 267UP راولپنڈی پسنجر267اپ
How late is it, usually?
no figure yet3 days recorded so far.
A typical (median) delay figure appears at 7 full days of recorded runs — days the train reported, not calendar days.
3 of 7 recorded days toward a first typical-delay figure
Where the time goes
most of it lost after RawalpindiLeaves Rawalpindi 54 min early · reaches Havelian +34 min — +1h 28m lost along the way.
- Rawalpindi08:00راولپِنڈى54 min early
- Golra Sharif08:19گولڑہ شریف+23 min
- Taxila Cantt08:43ٹیکسلا کینٹ+46 min
- Kot Najib Ullah09:25کوٹ نجیب اللہ+47 min
- Haripur Hazara09:45ہری پور ہزارہ+43 min
- Serai Saleh10:01سرائے صالح+42 min
- Baldher10:28بالھدر+34 min
- Havelian10:50حویلیاں+34 min
Where it stands longest past the timetableshortest to longest recorded
- Taxila Canttscheduled 2 min2–6 min
- Baldherscheduled 1 min1–5 min
- Golra Sharifscheduled 2 min1 min–2h 07m
- Kot Najib Ullahscheduled 1 min1–4 min
- Serai Salehscheduled 1 min1–8 min
What the marks mean
- Solid bar — the typical delay at that stop (median of recorded arrivals)
- Faint bar behind — the bad day (90th percentile): worse than nine tenths of recorded arrivals here
- No faint bar — fewer than 7 recorded arrivals at that stop, too thin for a 90th percentile. The solid bar can still show: it needs only 3.
- — (no solid bar either) — fewer than 3 recorded runs at that stop
- A negative figure means the train typically ran early at that stop, not late
- Band — the shortest and the longest stand recorded at that stop. The train has left as early as the first figure.
- Keyline — the scheduled stop, arrival to departure on the timetable below.
- Why a train stands is not recorded — a crossing, a loco change and a red signal all look the same on the clock.
- The five stops that stand longest past the timetable, not every stop — most routes have more. A stop qualifies with 7 or more runs timed in and out, and is skipped where the timetable books no stop, books one over an hour, or where any recorded stand ran past three hours.
- Most time is lost between Rawalpindi and Golra Sharif (+1h 17m)
- Every stop on the current timetable is listed, in order, measured or not.
Timetable
scheduled → actual, 8 October 2026 runThe second time in a cell is what actually happened on the 8 October 2026 run.
| # | Station | Arrival | Departure |
|---|---|---|---|
| 1 | Rawalpindi | — | 08:00 |
| 2 | Golra Sharif | 08:17 | 08:19 |
| 3 | Taxila Cantt | 08:41 → 09:32·PR | 08:43 → 09:36 |
| 4 | Kot Najib Ullah | 09:24 → 10:12·PR | 09:25 → 10:14 |
| 5 | Haripur Hazara | 09:40 → 10:21·PR | 09:45 → 10:39 |
| 6 | Serai Saleh | 10:00 → 10:50·PR | 10:01 → 10:51 |
| 7 | Baldher | 10:27 → 11:08·PR | 10:28 → 11:15 |
| 8 | Havelian | 10:50 → 11:27 | — |
What the marks mean
- → 21:28 — actual time on the 8 October 2026 run
- ·PR — Pakistan Railways' own record; unmarked is from the train's GPS
- +1d — the stop falls on a later day of the train's own run, counting from the day it starts. It is not a date.
- Blank — not recorded
A full recorded run: 23 August 2026 →
Station by station, last 5 days
27 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
2Golra Sharifscheduled 08:17+21m4 days
Day Arrived Delay Recorded by Thu 8 Oct arrived, time not recorded +31m Pakistan Railways Fri 2 Oct not recorded — Wed 30 Sept 08:46 +28m Pakistan Railways Mon 7 Sept 08:30 +13m Pakistan Railways (journey record) Sun 6 Sept 08:28 +12m Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +12m to +31m. Every train at Golra Sharif →
3Taxila Canttscheduled 08:41+35m4 days
Day Arrived Delay Recorded by Thu 8 Oct 09:32 +49m Pakistan Railways Fri 2 Oct not recorded — Wed 30 Sept 09:30 +47m Pakistan Railways Mon 7 Sept 09:04 +23m Pakistan Railways (journey record) Sun 6 Sept 09:03 +22m Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +22m to +49m. Every train at Taxila Cantt →
4Kot Najib Ullahscheduled 09:24+45m3 days
Day Arrived Delay Recorded by Thu 8 Oct 10:12 +48m Pakistan Railways Fri 2 Oct not recorded — Wed 30 Sept 10:08 +45m Pakistan Railways Mon 7 Sept not recorded — Sun 6 Sept 09:43 +20m Pakistan Railways (journey record) Seen on 3 of 5 days, ranging +20m to +48m. Every train at Kot Najib Ullah →
5Haripur Hazarascheduled 09:40+20m4 days
Day Arrived Delay Recorded by Thu 8 Oct 10:21 +26m Pakistan Railways Fri 2 Oct not recorded — Wed 30 Sept 10:16 +19m Pakistan Railways Mon 7 Sept 09:57 +17m Pakistan Railways (journey record) Sun 6 Sept 10:00 +21m Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +17m to +26m. Every train at Haripur Hazara →
6Serai Salehscheduled 10:00+27m4 days
Day Arrived Delay Recorded by Thu 8 Oct 10:50 +49m Pakistan Railways Fri 2 Oct not recorded — Wed 30 Sept 10:36 +35m Pakistan Railways Mon 7 Sept 10:13 +14m Pakistan Railways (journey record) Sun 6 Sept 10:18 +19m Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +14m to +49m. Every train at Serai Saleh →
7Baldherscheduled 10:27+20m4 days
Day Arrived Delay Recorded by Thu 8 Oct 11:08 +40m Pakistan Railways Fri 2 Oct not recorded — Wed 30 Sept 10:54 +26m Pakistan Railways Mon 7 Sept 10:33 +7m Pakistan Railways (journey record) Sun 6 Sept 10:39 +13m Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +7m to +40m. Every train at Baldher →
8Havelianscheduled 10:50+21m4 days
Day Arrived Delay Recorded by Thu 8 Oct 11:27 +37m Train GPS Fri 2 Oct not recorded — Wed 30 Sept 11:25 +35m Train GPS Mon 7 Sept 10:49 on time Pakistan Railways (journey record) Sun 6 Sept 10:57 +7m Pakistan Railways (journey record) Seen on 4 of 5 days, ranging on time to +37m. Every train at Havelian →
What the marks mean
- Tap a station — each day’s arrival, delay and recorder
- Green — within 15 minutes of the scheduled time
- Amber — 16 to 45 minutes late
- Red — over 45 minutes late
- Hollow — not recorded that day
- Grey — arrived, no delay figure
- Dash (—) — no delay figure for this stop yet
- Pakistan Railways — its own arrival record; Train GPS — measured from the train’s position
- The starting station is not listed — a train does not arrive where it begins.
Common questions
Is Rawalpindi Passenger 267UP usually late?
Typically 34 minutes late arriving at Havelian, measured across 20 recorded arrivals (1 Aug – 8 Oct 2026). That is the median, so half its runs were better than that and half were worse. It is what we recorded happening, not what the timetable books.
How late is Rawalpindi Passenger 267UP on a bad day?
On the worst one run in ten, 51 minutes late into Havelian, against a typical 34 minutes late. Both come from the same 20 recorded arrivals. A bad day is not the worst day we have ever seen; it is the level one run in ten reaches or passes.
What time does Rawalpindi Passenger 267UP leave Rawalpindi?
08:00, on the current published timetable. It is booked into Havelian at 10:50, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.
How long does Rawalpindi Passenger 267UP take from Rawalpindi to Havelian?
2h 50m on the timetable. In practice a typical run has taken 3h 24m, measured from recorded arrivals at Havelian.
How many stops does Rawalpindi Passenger 267UP make?
8 on the current published timetable, from Rawalpindi to Havelian. The full stop list, with the times booked at each one, is in the timetable on this page. Not every stop is recorded on every run: we publish arrivals we actually observed rather than filling the gaps.
Other trains on this route
All Rawalpindi–Havelian trains →Service history (first year, operating eras) is drawn from Wikipedia's List of Pakistan Railways trains, retrieved 15 August 2026, matched on train number.