42 Karakoram Express 42DN قراقرم ایکسپریس 42 ڈائون
How late is it, usually?
no figure yet6 days recorded so far.
A typical (median) delay figure appears at 7 full days of recorded runs — days the train reported, not calendar days.
6 of 7 recorded days toward a first typical-delay figure
Where the time goes
most of it lost after Lahore Jn.Leaves Lahore Jn. 14 min early · reaches Karachi Cantt +2h 32m — +2h 46m lost along the way.
- Lahore Jn.15:00لاہور جنکشن14 min early
- Faisalabad17:35فیصل آباد—
- Toba Tek Singh18:32ٹوبہ ٹیک سنگھ—
- Khanewal Jn20:25خانیوال31 min early
- Bahawalpur21:47بہاولپور+13 min
- Rohri Jn.02:50روہڑی جنکشن+1h 02m
- Hyderabad Jn07:35حیدرآباد جنکشن+1h 50m
- Landhi Jn.09:39لانڈھی جنکشن+2h 50m
- Drigh Road10:17ڈرگ روڈ+2h 40m
- Karachi Cantt10:45کراچی کينٹ+2h 32m
Where it stands longest past the timetableshortest to longest recorded
- Hyderabad Jnscheduled 5 min10 min–2h 52m
- Rohri Jn.scheduled 25 min23 min–1h 14m
- Bahawalpurscheduled 2 min3–12 min
- Drigh Roadscheduled 2 min2–14 min
- Landhi Jn.scheduled 2 min2–8 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 Hyderabad Jn and Landhi Jn. (+1h)
- 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 | Lahore Jn. | — | 15:00 |
| 2 | Faisalabad | 17:25 | 17:35 |
| 3 | Toba Tek Singh | 18:30 | 18:32 |
| 4 | Khanewal Jn | 20:05 → 19:37·PR | 20:25 → 20:20 |
| 5 | Bahawalpur | 21:45 → 21:49·PR | 21:47 → 21:50 |
| 6 | Rohri Jn. | 02:25 +1d → 03:34·PR | 02:50 +1d → 04:02 |
| 7 | Hyderabad Jn | 07:30 +1d → 09:36·PR | 07:35 +1d → 09:49 |
| 8 | Landhi Jn. | 09:37 +1d → 12:37·PR | 09:39 +1d → 12:39 |
| 9 | Drigh Road | 10:15 +1d → 12:59·PR | 10:17 +1d → 13:03 |
| 10 | Karachi Cantt | 10:45 +1d → 13:17 | — |
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: 22 August 2026 →
Station by station, last 5 days
31 arrivals recordedOne mark per day, newest first.
A run’s GPS trail is decoded after the journey completes — recent days may link later.
4Khanewal Jnscheduled 20:0551m early5 days
Day Arrived Delay Recorded by Thu 8 Oct 19:37 47m early Pakistan Railways Tue 6 Oct 19:32 52m early Pakistan Railways Sun 4 Oct 19:51 34m early Pakistan Railways Sat 3 Oct 19:31 53m early Pakistan Railways Thu 1 Oct 19:34 51m early Pakistan Railways Seen on 5 of 5 days, ranging 53m early to 34m early. Every train at Khanewal Jn →
5Bahawalpurscheduled 21:45+2m5 days
Day Arrived Delay Recorded by Thu 8 Oct 21:49 +2m Pakistan Railways Tue 6 Oct 22:00 +14m Pakistan Railways Sun 4 Oct 21:44 2m early Pakistan Railways Sat 3 Oct 21:42 5m early Pakistan Railways Thu 1 Oct 21:50 +3m Pakistan Railways Seen on 5 of 5 days, ranging 5m early to +14m. Every train at Bahawalpur →
6Rohri Jn.scheduled 02:25+46m5 days
Day Arrived Delay Recorded by Thu 8 Oct 03:34 +45m Pakistan Railways Tue 6 Oct 03:10 +21m Pakistan Railways Sun 4 Oct 03:11 +46m Pakistan Railways Sat 3 Oct 03:35 +46m Pakistan Railways Thu 1 Oct 03:11 +46m Pakistan Railways Seen on 5 of 5 days, ranging +21m to +46m. Every train at Rohri Jn. →
7Hyderabad Jnscheduled 07:30+1h135 days
Day Arrived Delay Recorded by Thu 8 Oct 09:36 +2h01 Pakistan Railways Tue 6 Oct 08:42 +1h07 Pakistan Railways Sun 4 Oct 08:34 +1h Pakistan Railways Sat 3 Oct 08:47 +1h13 Pakistan Railways Thu 1 Oct 09:19 +1h44 Pakistan Railways Seen on 5 of 5 days, ranging +1h to +2h01. Every train at Hyderabad Jn →
8Landhi Jn.scheduled 09:37+2h154 days
Day Arrived Delay Recorded by Thu 8 Oct 12:37 +2h58 Pakistan Railways Tue 6 Oct 11:11 +1h33 Pakistan Railways Sun 4 Oct 11:31 +1h53 Pakistan Railways Sat 3 Oct not recorded — Thu 1 Oct 12:14 +2h36 Pakistan Railways Seen on 4 of 5 days, ranging +1h33 to +2h58. Every train at Landhi Jn. →
9Drigh Roadscheduled 10:15+2h034 days
Day Arrived Delay Recorded by Thu 8 Oct 12:59 +2h43 Pakistan Railways Tue 6 Oct 11:32 +1h15 Pakistan Railways Sun 4 Oct 11:52 +1h35 Pakistan Railways Sat 3 Oct not recorded — Thu 1 Oct 12:48 +2h31 Pakistan Railways Seen on 4 of 5 days, ranging +1h15 to +2h43. Every train at Drigh Road →
10Karachi Canttscheduled 10:45+2h323 days
Day Arrived Delay Recorded by Thu 8 Oct 13:17 +2h32 Train GPS Tue 6 Oct 12:03 +1h18 Train GPS Sun 4 Oct not recorded — Sat 3 Oct not recorded — Thu 1 Oct 13:18 +2h33 Train GPS Seen on 3 of 5 days, ranging +1h18 to +2h33. Every train at Karachi Cantt →
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.
- 2 further stops on this route with nothing recorded yet — not listed.
Common questions
Is Karakoram Express 42DN usually late?
Typically 152 minutes late arriving at Karachi Cantt, measured across 18 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 Karakoram Express 42DN on a bad day?
On the worst one run in ten, 251 minutes late into Karachi Cantt, against a typical 152 minutes late. Both come from the same 18 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 Karakoram Express 42DN leave Lahore Jn.?
15:00, on the current published timetable. It is booked into Karachi Cantt at 10:45, the day after it leaves. Those are booked times. The delay figures on this page are what we recorded against them.
How long does Karakoram Express 42DN take from Lahore Jn. to Karachi Cantt?
19h 45m on the timetable. In practice a typical run has taken 22h 18m, measured from recorded arrivals at Karachi Cantt.
How many stops does Karakoram Express 42DN make?
10 on the current published timetable, from Lahore Jn. to Karachi Cantt. 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 Karakoram Express 42DN 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 Lahore–Karachi 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.