Lahore Jn. to Ghotki
Shalimar Express 28DN — within 15 minutes of the scheduled time 44% of the time, typically 22 minutes late, over 11 days of recorded runs across every stop of its full journey, not this segment alone. At Ghotki it has typically arrived 37 minutes late, from 35 recorded runs.
Every train, compared
7 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Lahore Jn. and Ghotki 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 29 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 | 21:22 | 15h 22m | not measured yet | +43 min | 14% | no data |
| 28Shalimar Express 28DN | 07:10 | 18:00 | 10h 50m | not measured yet | +22 min | 44% | no data |
| 2Khyber Mail 2DN | 07:35 +1d | 19:45 +1d | 12h 10m | 745 km | +2h 09m | 6% | adds 1h 51m · 14 |
| 10Allama Iqbal Express 10DN | 12:10 | 23:15 | 11h 05m | 687 km | +54 min | 25% | adds 1h 37m · 35 |
| 8Tezgam 8DN | 13:45 | 00:23 +1d | 10h 38m | 727 km | +52 min | 18% | adds 1h 46m · 37 |
| 40Jaffar Express 40DN | 16:45 | 03:23 +1d | 10h 38m | 740 km | +50 min | 25% | adds 1h 18m · 22 |
| 14Awam Express 14DN | 18:55 | 07:30 +1d | 12h 35m | 745 km | +2h 03m | 8% | adds 1h 38m · 34 |
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→21:2215h 22m14% on time · +43 minno data over this leg
- Shalimar Express 28DN28شالیمار ایکسپریس 28 ڈائون07:10→18:0010h 50m44% on time · +22 minno data over this leg
- Khyber Mail 2DN2خیبر میل 2 ڈائون07:35 +1d→19:45 +1d12h 10m6% on time · +2h 09madds 1h 51m over this leg · 14 runs
- Allama Iqbal Express 10DN10علامہ اقبال ایکسپریس 10 ڈائون12:10→23:1511h 05m25% on time · +54 minadds 1h 37m over this leg · 35 runs
- Tezgam 8DN8تیزگام 8 ڈاؤن13:45→00:23 +1d10h 38m18% on time · +52 minadds 1h 46m over this leg · 37 runs
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون16:45→03:23 +1d10h 38m25% on time · +50 minadds 1h 18m over this leg · 22 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون18:55→07:30 +1d12h 35m8% on time · +2h 03madds 1h 38m over this leg · 34 runs
Travelling the other way? Ghotki to Lahore Jn. trains →
Common questions
How many trains run from Lahore Jn. to Ghotki?
7 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 Ghotki?
Tezgam 8DN, booked at 10h 38m 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 Ghotki is most likely to be on time?
Shalimar Express 28DN has the best recorded punctuality of the services we hold enough history for: 44% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 22 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 7 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Lahore Jn. to Ghotki?
Yes. 3 of the 7 scheduled services are booked to arrive on a later day than they depart: Tezgam 8DN, Jaffar Express 40DN, Awam Express 14DN.
Do trains lose time between Lahore Jn. and Ghotki?
Typically yes. Khyber Mail 2DN adds about 1h 51m to its delay over this leg, measured across 14 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 Ghotki by train?
It is between 687 and 745 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 7 services; the rest of the track on this route has not been traced yet.
Are these Lahore Jn. to Ghotki 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.