311 YSW C (ENGINE NO 9014) یوسف والا کول42اپ
On time — heading for Khanpur Jn., due 23:53 (operator's estimate), stopped. Last crossed Rohri Jn..
How late is it, usually?
no figure yet3 days recorded so far.
A typical (median) delay figure appears at 7 full days of recorded runs — days the train reported, not calendar days.
3 of 7 recorded days toward a first typical-delay figure
Where the time goes
most of it lost after Marshalling Yard Pipri (Myp)Leaves Marshalling Yard Pipri (Myp) +5h 13m · reaches Yousuf Wala Railway Station +21h 33m — +16h 20m lost along the way.
- Marshalling Yard Pipri (Myp)08:15مارشلنگ یارڈ ( پپری)+5h 13m
- Kotri Jn11:20کوٹری جنکشن+11h 44m
- Rohri Jn.19:45روہڑی جنکشن+16h 42m
- Khanpur Jn.02:55خانپور جنکشن+34h 08m
- Samasata Jn07:45سمہ سٹہ جنکشن+28h 17m
- Khanewal Jn12:30خانیوال+24h 03m
- Yousuf Wala Railway Station16:10یوسف والا ریلوے اسٹیشن+21h 33m
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
- Most time is lost between Rohri Jn. and Khanpur Jn. (+17h 26m)
- Every stop on the current timetable is listed, in order, measured or not.
Timetable
scheduled → actual, 5 September 2026 runThe second time in a cell is what actually happened on the 5 September 2026 run.
| # | Station | Arrival | Departure |
|---|---|---|---|
| 1 | Marshalling Yard Pipri (Myp) | — | 08:15 |
| 2 | Kotri Jn | 11:00 | 11:20 |
| 3 | Rohri Jn. | 18:15 | 19:45 |
| 4 | Khanpur Jn. | 02:45 → 16:14 | 02:55 → 07:58 |
| 5 | Samasata Jn | 06:15 → 21:01 | 07:45 → 04:57 |
| 6 | Khanewal Jn | 12:00 → 05:18 | 12:30 → 22:02 |
| 7 | Yousuf Wala Railway Station | 16:10 → 10:24 | — → 18:01 |
What the marks mean
- → 21:28 — actual time on the 5 September 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
20 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 11:00+16h053 days
Day Arrived Delay Recorded by Fri 9 Oct arrived, time not recorded — Pakistan Railways Sun 4 Oct arrived, time not recorded +16h12 Pakistan Railways Thu 1 Oct 03:16 +15h58 Pakistan Railways Tue 29 Sept not recorded — Sat 5 Sept not recorded — Seen on 3 of 5 days, ranging +15h58 to +16h12. Every train at Kotri Jn →
3Rohri Jn.scheduled 18:15+17h354 days
Day Arrived Delay Recorded by Fri 9 Oct 14:26 — Pakistan Railways Sun 4 Oct 14:57 +19h12 Pakistan Railways Thu 1 Oct 13:20 +17h35 Pakistan Railways Tue 29 Sept arrived, time not recorded +2h57 Pakistan Railways Sat 5 Sept not recorded — Seen on 4 of 5 days, ranging +2h57 to +19h12. Every train at Rohri Jn. →
4Khanpur Jn.scheduled 02:45+35h534 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Sun 4 Oct 01:25 +46h31 Pakistan Railways Thu 1 Oct 21:21 +42h27 Pakistan Railways Tue 29 Sept 08:13 +29h19 Pakistan Railways Sat 5 Sept 16:14 +13h29 Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +13h29 to +46h31. Every train at Khanpur Jn. →
5Samasata Jnscheduled 06:15+37h354 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Sun 4 Oct 08:05 +48h20 Pakistan Railways Thu 1 Oct 03:13 +43h28 Pakistan Railways Tue 29 Sept 15:24 +31h41 Pakistan Railways Sat 5 Sept 21:01 +14h47 Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +14h47 to +48h20. Every train at Samasata Jn →
6Khanewal Jnscheduled 12:00+36h154 days
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Sun 4 Oct 14:55 +50h26 Pakistan Railways Thu 1 Oct 06:33 +42h03 Pakistan Railways Tue 29 Sept 18:56 +30h27 Pakistan Railways Sat 5 Sept 05:18 +17h19 Pakistan Railways (journey record) Seen on 4 of 5 days, ranging +17h19 to +50h26. Every train at Khanewal Jn →
7Yousuf Wala Railway Stationscheduled 16:10+18h141 day
Day Arrived Delay Recorded by Fri 9 Oct not recorded — Sun 4 Oct not recorded — Thu 1 Oct not recorded — Tue 29 Sept not recorded — Sat 5 Sept 10:24 +18h14 Pakistan Railways (journey record) Seen on 1 of 5 days. Every train at Yousuf Wala Railway Station →
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
What time does YSW C (ENGINE NO 9014) 311 UP leave Marshalling Yard Pipri (Myp)?
08:15, on the current published timetable. It is booked into Yousuf Wala Railway Station at 16:10, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.
How long does YSW C (ENGINE NO 9014) 311 UP take from Marshalling Yard Pipri (Myp) to Yousuf Wala Railway Station?
7h 55m on the timetable. We do not yet hold enough recorded arrivals at Yousuf Wala Railway Station to say what it takes in practice.
How many stops does YSW C (ENGINE NO 9014) 311 UP make?
7 on the current published timetable, from Marshalling Yard Pipri (Myp) to Yousuf Wala Railway Station. 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 YSW C (ENGINE NO 9014) 311 UP 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.