Kot Lakhpat to Karachi Cantt
Allama Iqbal Express 10DN — within 15 minutes of the scheduled time 25% of the time, typically 54 minutes late, over 11 days of recorded runs across every stop of its full journey, not this segment alone. That is its whole-journey record, a different promise from this leg alone: over just Kot Lakhpat to Karachi Cantt it typically adds 2h 15m, from 20 recorded runs. At Karachi Cantt it has typically arrived 180 minutes late, from 23 recorded runs.
Every train, compared
5 of 5 with 7+ daysOver this leg is the CHANGE in a train's delay between Kot Lakhpat and Karachi Cantt on the same run — not how late it arrives; a train can run late through its whole journey and still show no change here. — means either too few recorded runs on this leg, or — permanently, for a train whose journey starts right here at Kot Lakhpat — no booked arrival at Kot Lakhpat to measure from at all. Figures cover runs recorded between 31 July 2026 and 6 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 38Fareed Express 38DN | 06:27 | 07:55 +1d | 25h 28m | not measured yet | +43 min | 14% | adds 1h 04m · 27 |
| 2Khyber Mail 2DN | 08:04 +1d | 05:15 +2d | 21h 11m | 1,253 km | +2h 09m | 6% | adds 2h 33m · 11 |
| 10Allama Iqbal Express 10DN | 12:30 | 09:15 +1d | 20h 45m | 1,205 km | +54 min | 25% | adds 2h 15m · 20 |
| 34Pak Business 34DN | 16:49 | 11:30 +1d | 18h 41m | 1,201 km | +59 min | 20% | adds 2h 08m · 23 |
| 14Awam Express 14DN | 19:22 | 19:25 +1d | 24h 03m | 1,253 km | +2h 03m | 8% | adds 1h 28m · 31 |
What the marks mean
- Departs · Arrives — scheduled local times, published Pakistan Railways timetable
- +1d — a stop on a later day of the train's own run, not a date
- Typical delay · On-time — the train's whole journey, not this segment alone; typical is the median of its recorded stop arrivals, and on-time is within 15 minutes of the scheduled time
- — — fewer than 7 days of recorded runs for that train
- Over this leg — the change in each train's delay between the two stations above, counted on runs recorded at both (a run whose two stations were logged a day apart is matched too, when that day-shifted leg length matches the train's usual one). “adds” means the train picked up extra delay over this stretch; “makes up” means it arrived less late than it left; “no change” means neither. The figure shown is the middle (median) run: no more than half of a train's counted runs did WORSE than it, and no more than half did better — never a claim that exactly half did either, which isn't always possible to state.
- A large “makes up” usually says more about the leg than the train: where several services on this page all recover time, the stretch is booked with room in it. It never means the train ran early — only that it was less late arriving than departing.
- — — in that column: fewer than 7 runs recorded at both stations on the leg's usual booked times, or — permanently, for a train whose journey starts at this page's origin station — no booked arrival there to measure from at all, which will not fill in with more archive age.
Every service in detail
Typical delay and on-time share are the train's whole journey, from 7+ days of recorded runs. Over this leg is the change in that train's delay between the two stations, from runs recorded at both.
- Fareed Express 38DN38فرید ایکسپریس 38 ڈائون06:27→07:55 +1d25h 28m14% on time · +43 minadds 1h 04m over this leg · 27 runs
- Khyber Mail 2DN2خیبر میل 2 ڈائون08:04 +1d→05:15 +2d21h 11m6% on time · +2h 09madds 2h 33m over this leg · 11 runs
- Allama Iqbal Express 10DN10علامہ اقبال ایکسپریس 10 ڈائون12:30→09:15 +1d20h 45m25% on time · +54 minadds 2h 15m over this leg · 20 runs
- Pak Business 34DN34پاک بزنس 34 ڈائون16:49→11:30 +1d18h 41m20% on time · +59 minadds 2h 08m over this leg · 23 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون19:22→19:25 +1d24h 03m8% on time · +2h 03madds 1h 28m over this leg · 31 runs
Travelling the other way? Karachi Cantt to Kot Lakhpat trains →
Common questions
How many trains run from Kot Lakhpat to Karachi Cantt?
5 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Kot Lakhpat to Karachi Cantt?
Pak Business 34DN, booked at 18h 41m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Kot Lakhpat to Karachi Cantt is most likely to be on time?
Allama Iqbal Express 10DN has the best recorded punctuality of the services we hold enough history for: 25% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 54 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 5 of 5 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Kot Lakhpat to Karachi Cantt?
Yes. All 5 scheduled services are booked to arrive on a later day than they depart: Fareed Express 38DN, Khyber Mail 2DN, Allama Iqbal Express 10DN, Pak Business 34DN and others.
Do trains lose time between Kot Lakhpat and Karachi Cantt?
Typically yes. Khyber Mail 2DN adds about 2h 33m to its delay over this leg, measured across 11 recorded runs. That is the CHANGE over the leg, not how late the train arrives: a train can run late its whole journey and add nothing here.
How far is it from Kot Lakhpat to Karachi Cantt by train?
It is between 1,201 and 1,253 km along the track, depending on the service. Measured by summing our own GPS traces of trains running the route, not the straight-line distance between the two stations, which is always shorter than the rails. That is measured on 4 of the 5 services; the rest of the track on this route has not been traced yet.
Are these Kot Lakhpat to Karachi Cantt timings the real arrival times?
No. The departure and arrival columns are what the published timetable books. The delay columns beside them are what we recorded actually happening, from the operator's own reports and from GPS traces of the trains. Where a delay figure is blank we do not yet hold enough recorded runs to publish one.