Lahore Jn. to Kot Lakhpat
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 Lahore Jn. to Kot Lakhpat it typically adds 28 min, from 35 recorded runs. At Kot Lakhpat it has typically arrived 40 minutes late, from 43 recorded runs.
Every train, compared
5 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Lahore Jn. and Kot Lakhpat 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 Lahore Jn. — no booked arrival at Lahore Jn. to measure from at all. Figures cover runs recorded between 30 July 2026 and 7 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:00 | 06:25 | 25 min | not measured yet | +43 min | 14% | no data |
| 2Khyber Mail 2DN | 07:35 +1d | 08:02 +1d | 27 min | 23 km | +2h 09m | 6% | adds 21 min · 14 |
| 10Allama Iqbal Express 10DN | 12:10 | 12:28 | 18 min | 14 km | +54 min | 25% | adds 28 min · 35 |
| 258Bhullhe Shah passengers 258Dn | 16:00 | 16:28 | 28 min | 14 km | — | — | no data |
| 34Pak Business 34DN | 16:30 | 16:47 | 17 min | 14 km | +59 min | 20% | no data |
| 14Awam Express 14DN | 18:55 | 19:20 | 25 min | 23 km | +2h 03m | 8% | adds 32 min · 35 |
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:00→06:2525 min14% on time · +43 minno data over this leg
- Khyber Mail 2DN2خیبر میل 2 ڈائون07:35 +1d→08:02 +1d27 min6% on time · +2h 09madds 21 min over this leg · 14 runs
- Allama Iqbal Express 10DN10علامہ اقبال ایکسپریس 10 ڈائون12:10→12:2818 min25% on time · +54 minadds 28 min over this leg · 35 runs
- Bhullhe Shah passengers 258Dn258بھلے شاہ پسنجرز 258 ڈاؤن16:00→16:2828 minno delay figure yetno data over this leg
- Pak Business 34DN34پاک بزنس 34 ڈائون16:30→16:4717 min20% on time · +59 minno data over this leg
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون18:55→19:2025 min8% on time · +2h 03madds 32 min over this leg · 35 runs
Travelling the other way? Kot Lakhpat to Lahore Jn. trains →
Common questions
How many trains run from Lahore Jn. to Kot Lakhpat?
6 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Lahore Jn. to Kot Lakhpat?
Pak Business 34DN, booked at 17 min for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Lahore Jn. to Kot Lakhpat 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 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Lahore Jn. to Kot Lakhpat?
Not on the current timetable. Every service on this route is booked to arrive on the same day it departs.
Do trains lose time between Lahore Jn. and Kot Lakhpat?
Typically yes. Awam Express 14DN adds about 32 min to its delay over this leg, measured across 35 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 Lahore Jn. to Kot Lakhpat by train?
It is between 14 and 23 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 5 of the 6 services; the rest of the track on this route has not been traced yet.
Are these Lahore Jn. to Kot Lakhpat 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.