203 Jand Passenger 203up جنڈ پسنجر203اپ
How late is it, usually?
no figure yetOne day recorded so far.
A typical (median) delay figure appears at 7 full days of recorded runs — days the train reported, not calendar days.
1 of 7 recorded days toward a first typical-delay figure
Where the time goes
runs close to timeLeaves Langar +7 min · reaches Attock City Jn 2 min early — makes up +9 min.
- Jand Jn13:00جنڈ جنکشن—
- Langar13:09لنجار+7 min
- Chur Sharif13:17چرا شریف+5 min
- Nammal13:24نمل+6 min
- Domel13:38ڈومیل+6 min
- Basal Jn13:48بسال جنکشن+4 min
- Sulaimanbad14:00سلیمان آباد+6 min
- Jhalar14:08جھلار+7 min
- Attock City Jn14:40اٹک سٹی جنکشن2 min early
Where it stands longest past the timetableshortest to longest recorded
- Domelscheduled 1 min2–27 min
- Basal Jnscheduled 1 min1–57 min
- Sulaimanbadscheduled 1 min1–2 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 Basal Jn and Sulaimanbad (+2 min)
- Every stop on the current timetable is listed, in order, measured or not.
Timetable
scheduled → actual, 2 October 2026 runThe second time in a cell is what actually happened on the 2 October 2026 run.
| # | Station | Arrival | Departure |
|---|---|---|---|
| 1 | Jand Jn | — → 13:16·PR | 13:00 |
| 2 | Langar | 13:08 → 13:19·PR | 13:09 → 13:19 |
| 3 | Chur Sharif | 13:16 → 13:25·PR | 13:17 |
| 4 | Nammal | 13:23 → 13:31·PR | 13:24 |
| 5 | Domel | 13:37 | 13:38 |
| 6 | Basal Jn | 13:47 | 13:48 |
| 7 | Sulaimanbad | 13:59 | 14:00 |
| 8 | Jhalar | 14:07 | 14:08 |
| 9 | Attock City Jn | 14:40 → 14:36 | — → 14:37 |
What the marks mean
- → 21:28 — actual time on the 2 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
Station by station, last 5 days
15 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
2Langarscheduled 13:08+8m3 days
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct 13:19 +13m Pakistan Railways Mon 7 Sept 13:16 +8m Pakistan Railways (journey record) Sat 5 Sept not recorded — Wed 2 Sept 13:14 +6m Pakistan Railways (journey record) Seen on 3 of 5 days, ranging +6m to +13m. Every train at Langar →
3Chur Sharifscheduled 13:16+5m1 day
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct 13:25 +5m Pakistan Railways Mon 7 Sept not recorded — Sat 5 Sept not recorded — Wed 2 Sept not recorded — Seen on 1 of 5 days. Every train at Chur Sharif →
4Nammalscheduled 13:23+7m1 day
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct 13:31 +7m Pakistan Railways Mon 7 Sept not recorded — Sat 5 Sept not recorded — Wed 2 Sept not recorded — Seen on 1 of 5 days. Every train at Nammal →
5Domelscheduled 13:37+4m2 days
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct not recorded — Mon 7 Sept 13:43 +6m Pakistan Railways (journey record) Sat 5 Sept not recorded — Wed 2 Sept 13:37 +1m Pakistan Railways (journey record) Seen on 2 of 5 days, ranging +1m to +6m. Every train at Domel →
6Basal Jnscheduled 13:47—no figure
Day Arrived Delay Recorded by Sun 4 Oct arrived, time not recorded — Pakistan Railways Fri 2 Oct not recorded — Mon 7 Sept not recorded — Sat 5 Sept not recorded — Wed 2 Sept not recorded — Seen on 1 of 5 days. Every train at Basal Jn →
7Sulaimanbadscheduled 13:59+3m2 days
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct not recorded — Mon 7 Sept not recorded — Sat 5 Sept 14:04 +6m Pakistan Railways (journey record) Wed 2 Sept 13:59 on time Pakistan Railways (journey record) Seen on 2 of 5 days, ranging on time to +6m. Every train at Sulaimanbad →
8Jhalarscheduled 14:075m early1 day
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct arrived, time not recorded 5m early Pakistan Railways Mon 7 Sept not recorded — Sat 5 Sept not recorded — Wed 2 Sept not recorded — Seen on 1 of 5 days. Every train at Jhalar →
9Attock City Jnscheduled 14:403m early4 days
Day Arrived Delay Recorded by Sun 4 Oct not recorded — Fri 2 Oct 14:36 4m early Train GPS Mon 7 Sept 14:39 on time Pakistan Railways (journey record) Sat 5 Sept 14:38 2m early Pakistan Railways (journey record) Wed 2 Sept 14:29 10m early Pakistan Railways (journey record) Seen on 4 of 5 days, ranging 10m early to on time. Every train at Attock City 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 Jand Passenger 203up usually late?
Typically 2 minutes early arriving at Attock City Jn, measured across 15 recorded arrivals (31 Jul – 2 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 Jand Passenger 203up on a bad day?
On the worst one run in ten, 6 minutes late into Attock City Jn, against a typical 2 minutes early. Both come from the same 15 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 Jand Passenger 203up leave Jand Jn?
13:00, on the current published timetable. It is booked into Attock City Jn at 14:40, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.
How long does Jand Passenger 203up take from Jand Jn to Attock City Jn?
1h 40m on the timetable. In practice a typical run has taken 1h 38m, measured from recorded arrivals at Attock City Jn.
How many stops does Jand Passenger 203up make?
9 on the current published timetable, from Jand Jn to Attock City 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.
Other trains on this route
All Jand–Attock 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.