Subak Raftar 102DN — within 15 minutes of the scheduled time 41% of the time, typically 23 minutes late, over 10 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 Gujrat to Lahore Jn. it typically adds 28 min, from 23 recorded runs. At Lahore Jn. it has typically arrived 51 minutes late, from 29 recorded runs.
Every train, compared
6 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Gujrat and Lahore Jn. 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 Gujrat — no booked arrival at Gujrat to measure from at all. Figures cover runs recorded between 30 July 2026 and 1 October 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 2Khyber Mail 2DN | 05:04 +1d | 07:00 +1d | 1h 56m | 116 km | +2h 09m | 6% | adds 10 min · 14 |
| 102Subak Raftar 102DN | 10:09 | 11:50 | 1h 41m | 116 km | +23 min | 41% | adds 28 min · 23 |
| 8Tezgam 8DN | 11:24 | 13:15 | 1h 51m | 116 km | +52 min | 18% | adds 7 min · 38 |
| 40Jaffar Express 40DN | 14:12 | 16:10 | 1h 58m | 116 km | +50 min | 25% | makes up 5 min · 26 |
| 14Awam Express 14DN | 16:12 | 18:20 | 2h 08m | 116 km | +2h 03m | 8% | adds 19 min · 34 |
| 104Subak Kharam 104DN | 19:38 | 21:35 | 1h 57m | 116 km | +41 min | 28% | adds 4 min · 23 |
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.
- Khyber Mail 2DN2خیبر میل 2 ڈائون05:04 +1d→07:00 +1d1h 56m6% on time · +2h 09madds 10 min over this leg · 14 runs
- Subak Raftar 102DN102سبک رفتار102 ڈاؤن10:09→11:501h 41m41% on time · +23 minadds 28 min over this leg · 23 runs
- Tezgam 8DN8تیزگام 8 ڈاؤن11:24→13:151h 51m18% on time · +52 minadds 7 min over this leg · 38 runs
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون14:12→16:101h 58m25% on time · +50 minmakes up 5 min over this leg · 26 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون16:12→18:202h 08m8% on time · +2h 03madds 19 min over this leg · 34 runs
- Subak Kharam 104DN104سبک خرام 104 ڈاؤن19:38→21:351h 57m28% on time · +41 minadds 4 min over this leg · 23 runs
Travelling the other way? Lahore Jn. to Gujrat trains →
Common questions
How many trains run from Gujrat to Lahore Jn.?
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 Gujrat to Lahore Jn.?
Subak Raftar 102DN, booked at 1h 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 Gujrat to Lahore Jn. is most likely to be on time?
Subak Raftar 102DN has the best recorded punctuality of the services we hold enough history for: 41% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 23 min. That is its record across every stop of its full journey, not this leg alone: over just Gujrat to Lahore Jn. it typically adds 28 min, from 23 recorded runs. Measured from recorded runs, not from the timetable. 6 of 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Gujrat to Lahore Jn.?
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 Gujrat and Lahore Jn.?
Typically yes. Subak Raftar 102DN adds about 28 min to its delay over this leg, measured across 23 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 Gujrat to Lahore Jn. by train?
It is about 116 km along the track. 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.
Are these Gujrat to Lahore Jn. 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.