latetrains.pkLate, on record40 live
Trains/Rawalpindi–Lahore/Subak Raftar 102DN

102 Subak Raftar 102DN سبک رفتار102 ڈاؤن

Kitni late hoti hai? Typical delay, on-time record aur station timings.
RAWALPINDILAHORERAWALPINDI
Down direction · returnsراولپِنڈى ۔ لاہور جنکشن ۔ راولپِنڈى
In service since 2004ExpressLast seen 9 October 202668 days trackedLatest run →

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 Lahore Jn.+51 minmedian of 29 recorded arrivals · 4 Aug – 9 Oct 2026
Typical delay, any stop+23 minat a station this train calls at, not necessarily where you board · last 28 days
On time (within 15 min)41% of recorded stop arrivals
Bad day (90th percentile)+1h 13mworse than nine tenths of recorded stop arrivals

10 days of recorded arrivals.

Over 29 recorded arrivals (4 Aug – 9 Oct 2026), Subak Raftar 102DN has typically reached Lahore Jn. around 12:41 the day it leaves — on the worst one run in ten, past 13:44 the day it leaves, at Lahore Jn. itself. Latest run →

The “At Lahore Jn.” 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 4h 50m — Rawalpindi to Lahore Jn.. Typically 5h 41m, 51 min longer.

What these figures cover
  • Scheduled — the current timetable, Rawalpindi 07:00 to Lahore Jn. 11:50
  • Typical journey — from the scheduled departure to the recorded arrival at Lahore Jn.; the median of 29 runs
  • Bad day — 6h 44m 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: 4 August to 9 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+30 min · 4 runs
Tue+52 min · 3 runs
Wed+41 min · 4 runs
Thu+1h 30m · 4 runs
Fri+43 min · 5 runs
Sat+27 min · 5 runs
Sun+30 min · 4 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

most of it lost after Rawalpindi

Leaves Rawalpindi 20 min early · reaches Lahore Jn. +51 min — +1h 11m lost along the way.

  1. Rawalpindi07:00راولپِنڈى20 min early
  2. Chaklala07:10چکلالہ+5 min
  3. Jhelum08:58جہلم+24 min
  4. Lala Musa Jn.09:50لالہ مُوسٰی جنکشن+18 min
  5. Gujrat10:09گُجرات+26 min
  6. Wazirabad Jn10:27وزیرآباد جنکشن+29 min
  7. Gujranwala10:54گوجرانوالا+34 min
  8. Lahore Jn.11:50لاہور جنکشن+51 min

Where it stands longest past the timetableshortest to longest recorded

  1. Lala Musa Jn.scheduled 2 min3–21 min
  2. Jhelumscheduled 2 min3–15 min
  3. Gujranwalascheduled 2 min3–22 min
  4. Wazirabad Jnscheduled 2 min2–9 min
  5. Gujratscheduled 2 min2–15 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 Chaklala (+25 min)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 9 October 2026 run

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

#StationArrivalDeparture
1Rawalpindi—07:00
2Chaklala07:08 → 07:10·PR07:10 → 07:13
3Jhelum08:56 → 09:20·PR08:58 → 09:23
4Lala Musa Jn.09:48 → 10:02·PR09:50
5Gujrat10:07 → 10:27·PR10:09 → 10:31
6Wazirabad Jn10:25 → 10:46·PR10:27 → 10:53
7Gujranwala10:52 → 11:28·PR10:54 → 11:33
8Lahore Jn.11:50 → 12:31— → 12:33
What the marks mean
  • → 21:28 — actual time on the 9 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: 21 August 2026 →

Station by station, last 5 days

34 arrivals recorded

One mark per day, newest first.

Days shownFri9 OctThu8 OctWed7 OctTue6 OctMon5 Oct

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

  • 2Chaklalascheduled 07:08+4m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct07:10on timePakistan Railways
    Thu 8 Oct07:16+6mPakistan Railways
    Wed 7 Oct07:11+2mPakistan Railways
    Tue 6 Oct07:13+4mPakistan Railways
    Mon 5 Oct07:15+5mPakistan Railways

    Seen on 5 of 5 days, ranging on time to +6m. Every train at Chaklala →

  • 3Jhelumscheduled 08:56+24m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct09:20+24mPakistan Railways
    Thu 8 Oct09:18+23mPakistan Railways
    Wed 7 Oct09:19+24mPakistan Railways
    Tue 6 Oct09:19+23mPakistan Railways
    Mon 5 Oct09:38+40mPakistan Railways

    Seen on 5 of 5 days, ranging +23m to +40m. Every train at Jhelum →

  • 4Lala Musa Jn.scheduled 09:48+13m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct10:02+13mPakistan Railways
    Thu 8 Oct10:08+18mPakistan Railways
    Wed 7 Oct10:00+11mPakistan Railways
    Tue 6 Oct10:00+10mPakistan Railways
    Mon 5 Oct10:19+32mPakistan Railways

    Seen on 5 of 5 days, ranging +10m to +32m. Every train at Lala Musa Jn. →

  • 5Gujratscheduled 10:07+19m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct10:27+19mPakistan Railways
    Thu 8 Oct10:32+23mPakistan Railways
    Wed 7 Oct10:20+13mPakistan Railways
    Tue 6 Oct10:19+13mPakistan Railways
    Mon 5 Oct10:47+39mPakistan Railways

    Seen on 5 of 5 days, ranging +13m to +39m. Every train at Gujrat →

  • 6Wazirabad Jnscheduled 10:25+23m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct10:46+19mPakistan Railways
    Thu 8 Oct10:50+23mPakistan Railways
    Wed 7 Oct10:41+14mPakistan Railways
    Tue 6 Oct10:51+24mPakistan Railways
    Mon 5 Oct11:07+40mPakistan Railways

    Seen on 5 of 5 days, ranging +14m to +40m. Every train at Wazirabad Jn →

  • 7Gujranwalascheduled 10:52+31m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct11:28+34mPakistan Railways
    Thu 8 Oct11:20+26mPakistan Railways
    Wed 7 Oct11:11+17mPakistan Railways
    Tue 6 Oct11:25+31mPakistan Railways
    Mon 5 Oct11:39+45mPakistan Railways

    Seen on 5 of 5 days, ranging +17m to +45m. Every train at Gujranwala →

  • 8Lahore Jn.scheduled 11:50+40m4 days
    DayArrivedDelayRecorded by
    Fri 9 Oct12:31+41mTrain GPS
    Thu 8 Octnot recorded—
    Wed 7 Oct12:07+17mTrain GPS
    Tue 6 Oct12:27+38mTrain GPS
    Mon 5 Oct13:34+1h44Train GPS

    Seen on 4 of 5 days, ranging +17m to +1h44. Every train at Lahore Jn. →

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 Subak Raftar 102DN usually late?

Typically 51 minutes late arriving at Lahore Jn., measured across 29 recorded arrivals (4 Aug – 9 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 Subak Raftar 102DN on a bad day?

On the worst one run in ten, 114 minutes late into Lahore Jn., against a typical 51 minutes late. Both come from the same 29 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 Subak Raftar 102DN leave Rawalpindi?

07:00, on the current published timetable. It is booked into Lahore Jn. at 11:50, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does Subak Raftar 102DN take from Rawalpindi to Lahore Jn.?

4h 50m on the timetable. In practice a typical run has taken 5h 41m, measured from recorded arrivals at Lahore Jn..

How many stops does Subak Raftar 102DN make?

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

Where is Subak Raftar 102DN right now?

The live tracker for this train shows its last reported position and how late it was running at its most recent recorded stop. Position comes from the operator's own feed. When a train is not reporting we say so rather than estimating where it might be.

All Rawalpindi–Lahore 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. Further reading: the train's own Wikipedia article.