104 Subak Kharam 104DN سبک خرام 104 ڈاؤن
Running 36 min late — heading for Jhelum, due 19:06 (operator's estimate), 78 km/h. Last crossed Gujar Khan.
How late is it, usually?
median per recorded stop arrivalEvery 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.
9 days of recorded arrivals.
Over 33 recorded arrivals (1 Aug – 8 Oct 2026), Subak Kharam 104DN has typically reached Lahore Jn. around 22:21 the day it leaves — on the worst one run in ten, past 23:10 the day it leaves, at Lahore Jn. itself. Today's run: track it live →
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 recordedScheduled 5h 05m — Rawalpindi to Lahore Jn.. Typically 5h 51m, 46 min longer.
What these figures cover
- Scheduled — the current timetable, Rawalpindi 16:30 to Lahore Jn. 21:35
- Typical journey — from the scheduled departure to the recorded arrival at Lahore Jn.; the median of 33 runs
- Bad day — 6h 40m 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 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 windowThis 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 RawalpindiLeaves Rawalpindi 32 min early · reaches Lahore Jn. +46 min — +1h 18m lost along the way.
- Rawalpindi16:30راولپِنڈى32 min early
- Chaklala16:40چکلالہ+5 min
- Gujar Khan17:22گُوجر خان+26 min
- Jhelum18:32جہلم+32 min
- Lala Musa Jn.19:19لالہ مُوسٰی جنکشن+23 min
- Gujrat19:38گُجرات+40 min
- Wazirabad Jn20:00وزیرآباد جنکشن+42 min
- Gujranwala20:27گوجرانوالا+48 min
- Lahore Jn.21:35لاہور جنکشن+46 min
Where it stands longest past the timetableshortest to longest recorded
- Gujratscheduled 2 min2–23 min
- Lala Musa Jn.scheduled 2 min3–24 min
- Jhelumscheduled 2 min2–13 min
- Wazirabad Jnscheduled 2 min2–26 min
- Chaklalascheduled 2 min2–20 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 (+37 min)
- 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 | — | 16:30 |
| 2 | Chaklala | 16:38 → 16:44·PR | 16:40 → 16:46 |
| 3 | Gujar Khan | 17:20 → 18:14·PR | 17:22 |
| 4 | Jhelum | 18:30 → 19:27·PR | 18:32 → 19:31 |
| 5 | Lala Musa Jn. | 19:17 → 20:09·PR | 19:19 → 20:13 |
| 6 | Gujrat | 19:36 → 20:40·PR | 19:38 → 20:44 |
| 7 | Wazirabad Jn | 19:58 → 20:59·PR | 20:00 → 21:02 |
| 8 | Gujranwala | 20:25 → 21:29·PR | 20:27 → 21:32 |
| 9 | Lahore Jn. | 21:35 → 22:37 | — → 22:47 |
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: 21 August 2026 →
Station by station, last 5 days
34 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
2Chaklalascheduled 16:38+6m5 days
Day Arrived Delay Recorded by Fri 9 Oct 16:45 +6m Pakistan Railways Thu 8 Oct 16:44 +4m Pakistan Railways Wed 7 Oct 16:41 +3m Pakistan Railways Tue 6 Oct 16:46 +6m Pakistan Railways Mon 5 Oct arrived, time not recorded +9m Pakistan Railways Seen on 5 of 5 days, ranging +3m to +9m. Every train at Chaklala →
3Gujar Khanscheduled 17:20+32m5 days
Day Arrived Delay Recorded by Fri 9 Oct 17:55 +28m Pakistan Railways Thu 8 Oct 18:14 +53m Pakistan Railways Wed 7 Oct 17:50 +30m Pakistan Railways Tue 6 Oct 17:54 +32m Pakistan Railways Mon 5 Oct 18:08 +46m Pakistan Railways Seen on 5 of 5 days, ranging +28m to +53m. Every train at Gujar Khan →
4Jhelumscheduled 18:30+48m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 19:27 +56m Pakistan Railways Wed 7 Oct 19:10 +34m Pakistan Railways Tue 6 Oct 19:17 +48m Pakistan Railways Mon 5 Oct 19:17 +48m Pakistan Railways Seen on 4 of 5 days, ranging +34m to +56m. Every train at Jhelum →
5Lala Musa Jn.scheduled 19:17+55m4 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 20:09 +51m Pakistan Railways Wed 7 Oct 19:46 +27m Pakistan Railways Tue 6 Oct 20:17 +58m Pakistan Railways Mon 5 Oct 20:19 +1h02 Pakistan Railways Seen on 4 of 5 days, ranging +27m to +1h02. Every train at Lala Musa Jn. →
6Gujratscheduled 19:36+1h054 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 20:40 +1h03 Pakistan Railways Wed 7 Oct 20:10 +32m Pakistan Railways Tue 6 Oct 20:46 +1h08 Pakistan Railways Mon 5 Oct 20:45 +1h07 Pakistan Railways Seen on 4 of 5 days, ranging +32m to +1h08. Every train at Gujrat →
7Wazirabad Jnscheduled 19:58+1h014 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 20:59 +59m Pakistan Railways Wed 7 Oct 20:29 +29m Pakistan Railways Tue 6 Oct 21:04 +1h05 Pakistan Railways Mon 5 Oct 21:03 +1h03 Pakistan Railways Seen on 4 of 5 days, ranging +29m to +1h05. Every train at Wazirabad Jn →
8Gujranwalascheduled 20:25+1h044 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 21:29 +1h02 Pakistan Railways Wed 7 Oct 21:03 +36m Pakistan Railways Tue 6 Oct 21:44 +1h17 Pakistan Railways Mon 5 Oct 21:32 +1h06 Pakistan Railways Seen on 4 of 5 days, ranging +36m to +1h17. Every train at Gujranwala →
9Lahore Jn.scheduled 21:35+1h184 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Thu 8 Oct 22:37 +1h02 Train GPS Wed 7 Oct 23:12 +1h37 Train GPS Tue 6 Oct 23:01 +1h27 Train GPS Mon 5 Oct 22:44 +1h09 Train GPS Seen on 4 of 5 days, ranging +1h02 to +1h37. 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 Kharam 104DN usually late?
Typically 46 minutes late arriving at Lahore Jn., measured across 33 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 Subak Kharam 104DN on a bad day?
On the worst one run in ten, 95 minutes late into Lahore Jn., against a typical 46 minutes late. Both come from the same 33 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 104DN leave Rawalpindi?
16:30, on the current published timetable. It is booked into Lahore Jn. at 21:35, 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 104DN take from Rawalpindi to Lahore Jn.?
5h 05m on the timetable. In practice a typical run has taken 5h 51m, measured from recorded arrivals at Lahore Jn..
How many stops does Subak Kharam 104DN make?
9 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 Kharam 104DN 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.
Other trains on this route
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.