501 501 UP (ENGINE NUM 9001) سپر پارسل 501 اپ
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
Timetable
scheduled → actual, 23 August 2026 runThe second time in a cell is what actually happened on the 23 August 2026 run.
| # | Station | Arrival | Departure |
|---|---|---|---|
| 1 | Karachi City | — → 01:41 | 01:00 → 02:11 |
| 2 | Kotri Jn | 04:35 → 07:09 | 04:55 → 08:22 |
| 3 | Tando Adam | 06:15 | 06:25 |
| 4 | Rohri Jn. | 12:00 | 13:30 |
| 5 | Khanpur Jn. | 18:40 | 18:50 |
| 6 | Samasata Jn | 22:15 | 23:45 |
| 7 | Khanewal Jn | 02:20 | 02:30 |
| 8 | Shorkot Cantt Jn | 03:50 | 04:00 |
| 9 | Faisalabad | 07:05 | 07:15 |
| 10 | Badami Bagh | 10:15 | — |
What the marks mean
- → 21:28 — actual time on the 23 August 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 3 days
11 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
2Kotri Jnscheduled 04:35+50h343 days
Day Arrived Delay Recorded by Sun 23 Aug 07:09 +50h34 Pakistan Railways (journey record) Wed 12 Aug 09:10 +4h30 Pakistan Railways Sat 8 Aug 21:13 +64h38 Pakistan Railways (journey record) Seen on 3 of 3 days, ranging +4h30 to +64h38. Every train at Kotri Jn →
3Tando Adamscheduled 06:15+33h222 days
Day Arrived Delay Recorded by Sun 23 Aug not recorded — Wed 12 Aug 10:47 +6h59 Pakistan Railways Sat 8 Aug 18:00 +59h45 Pakistan Railways (journey record) Seen on 2 of 3 days, ranging +6h59 to +59h45. Every train at Tando Adam →
4Rohri Jn.scheduled 12:00+8h262 days
Day Arrived Delay Recorded by Sun 23 Aug not recorded — Wed 12 Aug 18:58 +5h32 Pakistan Railways Sat 8 Aug 23:19 +11h20 Pakistan Railways (journey record) Seen on 2 of 3 days, ranging +5h32 to +11h20. Every train at Rohri Jn. →
5Khanpur Jn.scheduled 18:40+17h092 days
Day Arrived Delay Recorded by Sun 23 Aug not recorded — Wed 12 Aug arrived, time not recorded +15h14 Pakistan Railways Sat 8 Aug 13:43 +19h04 Pakistan Railways (journey record) Seen on 2 of 3 days, ranging +15h14 to +19h04. Every train at Khanpur Jn. →
6Samasata Jnscheduled 22:15+13h552 days
Day Arrived Delay Recorded by Sun 23 Aug not recorded — Wed 12 Aug 07:45 +9h31 Pakistan Railways (journey record) Sat 8 Aug 16:32 +18h18 Pakistan Railways (journey record) Seen on 2 of 3 days, ranging +9h31 to +18h18. Every train at Samasata 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.
- 4 further stops on this route with nothing recorded yet — not listed.
Common questions
What time does 501 UP (ENGINE NUM 9001) leave Karachi City?
01:00, on the current published timetable. It is booked into Badami Bagh at 10:15, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.
How long does 501 UP (ENGINE NUM 9001) take from Karachi City to Badami Bagh?
9h 15m on the timetable. We do not yet hold enough recorded arrivals at Badami Bagh to say what it takes in practice.
How many stops does 501 UP (ENGINE NUM 9001) make?
10 on the current published timetable, from Karachi City to Badami Bagh. 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.