latetrains.pkLate, on record44 live
Trains/Lahore–Rawalpindi/Subak Kharam 103UP

103 Subak Kharam 103UP سبک خرم 103 اپ

Kitni late hoti hai? Typical delay, on-time record aur station timings.
LAHORERAWALPINDILAHORE
Up direction · returnsلاہور جنکشن ۔ راولپِنڈى ۔ لاہور جنکشن
In service since 2004ExpressLast seen 9 October 202671 days trackedTrack it live →
Live running status — right nowLive · 27 sec · official GPS

Running 36 min late — heading for Gujrat, due 19:09 (operator's estimate), stopped. Last crossed Wazirabad Jn.

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+45 minmedian of 35 recorded arrivals · 31 Jul – 8 Oct 2026
Typical delay, any stop+20 minat a station this train calls at, not necessarily where you board · last 28 days
On time (within 15 min)46% of recorded stop arrivals
Bad day (90th percentile)+1h 11mworse than nine tenths of recorded stop arrivals

9 days of recorded arrivals.

Over 35 recorded arrivals (31 Jul – 8 Oct 2026), Subak Kharam 103UP has typically reached Rawalpindi around 22:25 the day it leaves — on the worst one run in ten, past 22:59 the day it leaves, at Rawalpindi itself. Today's run: track it live →

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 5h 10m — Lahore Jn. to Rawalpindi. Typically 5h 55m, 45 min longer.

What these figures cover
  • Scheduled — the current timetable, Lahore Jn. 16:30 to Rawalpindi 21:40
  • Typical journey — from the scheduled departure to the recorded arrival at Rawalpindi; the median of 35 runs
  • Bad day — 6h 29m 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: 31 July to 8 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+23 min · 4 runs
Tue+22 min · 4 runs
Wed+28 min · 4 runs
Thu+35 min · 4 runs
Fri+27 min · 5 runs
Sat+28 min · 5 runs
Sun+25 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 Lahore Jn.

Leaves Lahore Jn. 36 min early · reaches Rawalpindi +45 min — +1h 21m lost along the way.

  1. Lahore Jn.16:30لاہور جنکشن36 min early
  2. Gujranwala17:35گوجرانوالا+6 min
  3. Wazirabad Jn18:07وزیرآباد جنکشن+14 min
  4. Gujrat18:35گُجرات+8 min
  5. Lala Musa Jn.18:57لالہ مُوسٰی جنکشن+16 min
  6. Jhelum19:38جہلم+33 min
  7. Chaklala21:32چکلالہ+46 min
  8. Rawalpindi21:40راولپِنڈى+45 min

Where it stands longest past the timetableshortest to longest recorded

  1. Gujratscheduled 2 min2–44 min
  2. Lala Musa Jn.scheduled 2 min2–17 min
  3. Gujranwalascheduled 2 min1–25 min
  4. Jhelumscheduled 2 min2–17 min
  5. Wazirabad Jnscheduled 2 min2–13 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 Lahore Jn. and Gujranwala (+42 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
1Lahore Jn.—16:30
2Gujranwala17:33 → 18:13·PR17:35 → 18:13
3Wazirabad Jn18:05 → 18:43·PR18:07
4Gujrat18:3318:35
5Lala Musa Jn.18:5518:57
6Jhelum19:3619:38
7Chaklala21:3021:32
8Rawalpindi21:40—
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: 20 August 2026 →

Station by station, last 5 days

30 arrivals recorded

One mark per day, newest first.

Days shownFri9 OctThu8 OctWed7 OctMon5 OctSun4 Oct

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

  • 2Gujranwalascheduled 17:33+1m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct18:13+39mPakistan Railways
    Thu 8 Oct17:322m earlyPakistan Railways
    Wed 7 Oct17:322m earlyPakistan Railways
    Mon 5 Oct17:45+11mPakistan Railways
    Sun 4 Oct17:35+1mPakistan Railways

    Seen on 5 of 5 days, ranging 2m early to +39m. Every train at Gujranwala →

  • 3Wazirabad Jnscheduled 18:05+11m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct18:43+36mPakistan Railways
    Thu 8 Oct18:09+3mPakistan Railways
    Wed 7 Oct18:17+11mPakistan Railways
    Mon 5 Oct18:33+26mPakistan Railways
    Sun 4 Oct18:14+7mPakistan Railways

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

  • 4Gujratscheduled 18:33+15m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct19:02+28mPakistan Railways
    Wed 7 Oct18:37+2mPakistan Railways
    Mon 5 Oct19:07+32mPakistan Railways
    Sun 4 Oct18:331m earlyPakistan Railways

    Seen on 4 of 5 days, ranging 1m early to +32m. Every train at Gujrat →

  • 5Lala Musa Jn.scheduled 18:55+21m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct19:28+32mPakistan Railways
    Wed 7 Oct18:57+1mPakistan Railways
    Mon 5 Oct19:41+44mPakistan Railways
    Sun 4 Oct19:06+9mPakistan Railways

    Seen on 4 of 5 days, ranging +1m to +44m. Every train at Lala Musa Jn. →

  • 6Jhelumscheduled 19:36+26m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct20:15+37mPakistan Railways
    Wed 7 Oct19:51+14mPakistan Railways
    Mon 5 Oct21:10+1h32Pakistan Railways
    Sun 4 Oct19:42+4mPakistan Railways

    Seen on 4 of 5 days, ranging +4m to +1h32. Every train at Jhelum →

  • 7Chaklalascheduled 21:30+56m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct22:42+1h10Pakistan Railways
    Wed 7 Oct22:10+38mPakistan Railways
    Mon 5 Oct23:15+1h46Pakistan Railways
    Sun 4 Oct22:13+41mPakistan Railways

    Seen on 4 of 5 days, ranging +38m to +1h46. Every train at Chaklala →

  • 8Rawalpindischeduled 21:40+1h4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct22:55+1h15Train GPS
    Wed 7 Oct22:22+43mTrain GPS
    Mon 5 Oct23:29+1h49Train GPS
    Sun 4 Oct22:25+45mTrain GPS

    Seen on 4 of 5 days, ranging +43m to +1h49. 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 Subak Kharam 103UP usually late?

Typically 45 minutes late arriving at Rawalpindi, measured across 35 recorded arrivals (31 Jul – 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 Subak Kharam 103UP on a bad day?

On the worst one run in ten, 79 minutes late into Rawalpindi, against a typical 45 minutes late. Both come from the same 35 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 Kharam 103UP leave Lahore Jn.?

16:30, on the current published timetable. It is booked into Rawalpindi at 21:40, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does Subak Kharam 103UP take from Lahore Jn. to Rawalpindi?

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

How many stops does Subak Kharam 103UP make?

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

Where is Subak Kharam 103UP 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 Lahore–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. Further reading: the train's own Wikipedia article.