latetrains.pkLate, on record43 live
Trains/Havelian–Rawalpindi/Rawalpindi Passenger 268DN

268 Rawalpindi Passenger 268DN راولپنڈی پسنجر 268ڈاؤن

Kitni late hoti hai? Typical delay, on-time record aur station timings.
HAVELIANRAWALPINDIHAVELIAN
Down direction · returnsحویلیاں ۔ راولپِنڈى ۔ حویلیاں
PassengerLast seen 8 October 202669 days tracked

How late is it, usually?

median per recorded stop arrival

Every figure here is a median, not an average: why we publish a median, not an average. What counts as on time, and why some figures here are blank, is set out in what on time means here, and every threshold behind it.

At Rawalpindi+2h 47mmedian of 19 recorded arrivals · 1 Aug – 6 Oct 2026
Typical delay, any stop+2h 48mat a station this train calls at, not necessarily where you board · last 28 days
On time (within 15 min)0% of recorded stop arrivals
Bad day (90th percentile)+7h 52mworse than nine tenths of recorded stop arrivals

7 days of recorded arrivals.

Over 19 recorded arrivals (1 Aug – 6 Oct 2026), Rawalpindi Passenger 268DN has typically reached Rawalpindi around 23:52 the day it leaves — on the worst one run in ten, past 01:15 the day after it leaves, at Rawalpindi itself.

The “At Rawalpindi” tile above is the arrival at the end of the run; “Typical delay, any stop” averages every stop including the earlier ones, so it usually reads smaller. Where the time goes, below, shows every stop we have recorded.

How long does it take?

scheduled vs recorded

Scheduled 2h 50m — Havelian to Rawalpindi. Typically 5h 37m, 2h 47m longer.

What these figures cover
  • Scheduled — the current timetable, Havelian 18:15 to Rawalpindi 21:05
  • Typical journey — from the scheduled departure to the recorded arrival at Rawalpindi; the median of 19 runs
  • Bad day — 7h at the 90th percentile: nine runs in ten come in under it
  • Keyline — the scheduled time. The solid bar is the typical journey, the faint bar behind it the bad day.
  • Recorded arrivals: 1 August to 6 October 2026.
  • End to end. For a shorter leg, the stop times are in the timetable below.

Which day is worst?

mean minutes late per recorded arrival, 8-week window
Mon+2h 17m · 5 runs
Tue+2h 20m · 3 runs
Wed+3h 24m · 4 runs
Thuno data
Frino data
Sat+4h 54m · 3 runs
Sun+2h 15m · 3 runs

This is a mean over an 8-week window, not the median (typical) figure above — the two are not directly comparable.

Where the time goes

already late at Havelian

Leaves Havelian +3h 11m · reaches Rawalpindi +2h 47m — makes up +24 min.

  1. Havelian18:15حویلیاں+3h 11m
  2. Baldher18:34بالھدر+2h 58m
  3. Serai Saleh18:58سرائے صالح+2h 52m
  4. Haripur Hazara19:20ہری پور ہزارہ+2h 48m
  5. Kot Najib Ullah19:36کوٹ نجیب اللہ+2h 48m
  6. Taxila Cantt20:19ٹیکسلا کینٹ+2h 38m
  7. Golra Sharif20:42گولڑہ شریف+2h 56m
  8. Rawalpindi21:05راولپِنڈى+2h 47m

Where it stands longest past the timetableshortest to longest recorded

  1. Taxila Canttscheduled 2 min1–54 min
  2. Kot Najib Ullahscheduled 1 min1–10 min
  3. Baldherscheduled 1 min1–6 min
  4. Serai Salehscheduled 1 min1–2 min
  5. Golra Sharifscheduled 2 min1–27 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 Taxila Cantt and Golra Sharif (+18 min)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 7 October 2026 run

The second time in a cell is what actually happened on the 7 October 2026 run.

#StationArrivalDeparture
1Havelian—18:15
2Baldher18:33 → 23:44·PR18:34 → 23:45
3Serai Saleh18:57 → 00:05·PR18:58
4Haripur Hazara19:15 → 00:19·PR19:20 → 00:19
5Kot Najib Ullah19:35 → 00:37·PR19:36
6Taxila Cantt20:17 → 01:03·PR20:19 → 01:17
7Golra Sharif20:40 → 01:57·PR20:42 → 01:59
8Rawalpindi21:05—
What the marks mean
  • → 21:28 — actual time on the 7 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: 19 August 2026 →

Station by station, last 5 days

33 arrivals recorded

One mark per day, newest first.

Days shownWed7 OctTue6 OctMon5 OctSun4 OctSat3 Oct

A run’s GPS trail is decoded after the journey completes — recent days may link later.

  • 2Baldherscheduled 18:33+2h595 days
    DayArrivedDelayRecorded by
    Wed 7 Oct23:44+5h10Pakistan Railways
    Tue 6 Oct21:32+2h59Pakistan Railways
    Mon 5 Oct20:20+1h48Pakistan Railways
    Sun 4 Oct20:13+1h40Pakistan Railways
    Sat 3 Oct03:10+8h36Pakistan Railways

    Seen on 5 of 5 days, ranging +1h40 to +8h36. Every train at Baldher →

  • 3Serai Salehscheduled 18:57+2h555 days
    DayArrivedDelayRecorded by
    Wed 7 Oct00:05+5h08Pakistan Railways
    Tue 6 Oct21:53+2h55Pakistan Railways
    Mon 5 Oct20:43+1h45Pakistan Railways
    Sun 4 Oct20:30+1h32Pakistan Railways
    Sat 3 Oct03:28+8h31Pakistan Railways

    Seen on 5 of 5 days, ranging +1h32 to +8h31. Every train at Serai Saleh →

  • 4Haripur Hazarascheduled 19:15+2h485 days
    DayArrivedDelayRecorded by
    Wed 7 Oct00:19+4h59Pakistan Railways
    Tue 6 Oct22:07+2h48Pakistan Railways
    Mon 5 Oct20:56+1h36Pakistan Railways
    Sun 4 Oct20:40+1h21Pakistan Railways
    Sat 3 Oct03:42+8h23Pakistan Railways

    Seen on 5 of 5 days, ranging +1h21 to +8h23. Every train at Haripur Hazara →

  • 5Kot Najib Ullahscheduled 19:35+2h525 days
    DayArrivedDelayRecorded by
    Wed 7 Oct00:37+5h02Pakistan Railways
    Tue 6 Oct22:28+2h52Pakistan Railways
    Mon 5 Oct21:16+1h40Pakistan Railways
    Sun 4 Oct20:56+1h21Pakistan Railways
    Sat 3 Oct03:59+8h24Pakistan Railways

    Seen on 5 of 5 days, ranging +1h21 to +8h24. Every train at Kot Najib Ullah →

  • 6Taxila Canttscheduled 20:17+2h235 days
    DayArrivedDelayRecorded by
    Wed 7 Oct01:03+4h35Pakistan Railways
    Tue 6 Oct22:51+2h23Pakistan Railways
    Mon 5 Oct21:41+1h13Pakistan Railways
    Sun 4 Oct21:18+50mPakistan Railways
    Sat 3 Oct04:23+7h54Pakistan Railways

    Seen on 5 of 5 days, ranging +50m to +7h54. Every train at Taxila Cantt →

  • 7Golra Sharifscheduled 20:40+3h215 days
    DayArrivedDelayRecorded by
    Wed 7 Oct01:57+5h16Pakistan Railways
    Tue 6 Oct00:03+3h21Pakistan Railways
    Mon 5 Oct22:32+1h51Pakistan Railways
    Sun 4 Oct22:04+1h22Pakistan Railways
    Sat 3 Oct05:15+8h33Pakistan Railways

    Seen on 5 of 5 days, ranging +1h22 to +8h33. Every train at Golra Sharif →

  • 8Rawalpindischeduled 21:05+2h033 days
    DayArrivedDelayRecorded by
    Wed 7 Octnot recorded—
    Tue 6 Oct00:28+3h24Train GPS
    Mon 5 Oct23:07+2h03Train GPS
    Sun 4 Oct22:29+1h25Train GPS
    Sat 3 Octnot recorded—

    Seen on 3 of 5 days, ranging +1h25 to +3h24. Every train at Rawalpindi →

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 268DN usually late?

Typically 167 minutes late arriving at Rawalpindi, measured across 19 recorded arrivals (1 Aug – 6 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 268DN on a bad day?

On the worst one run in ten, 250 minutes late into Rawalpindi, against a typical 167 minutes late. Both come from the same 19 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 268DN leave Havelian?

18:15, on the current published timetable. It is booked into Rawalpindi at 21:05, 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 268DN take from Havelian to Rawalpindi?

2h 50m on the timetable. In practice a typical run has taken 5h 37m, measured from recorded arrivals at Rawalpindi.

How many stops does Rawalpindi Passenger 268DN make?

8 on the current published timetable, from Havelian to Rawalpindi. 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.

All Havelian–Rawalpindi 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.