Rawalpindi to Landhi Jn.
Tezgam 8DN — within 15 minutes of the scheduled time 18% of the time, typically 52 minutes late, over 10 days of recorded runs across every stop of its full journey, not this segment alone. At Landhi Jn. it has typically arrived 224 minutes late, from 48 recorded runs.
Every train, compared
6 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Rawalpindi and Landhi 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 Rawalpindi — no booked arrival at Rawalpindi 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 |
|---|---|---|---|---|---|---|---|
| 2Khyber Mail 2DN | 01:50 +1d | 04:08 +2d | 26h 18m | 1,545 km | +2h 09m | 6% | no data |
| 46Pakistan Express 46DN | 06:00 | 07:42 +1d | 25h 42m | 1,474 km | +1h 05m | 6% | no data |
| 8Tezgam 8DN | 08:00 | 09:15 +1d | 25h 15m | 1,529 km | +52 min | 18% | no data |
| 14Awam Express 14DN | 12:30 | 18:16 +1d | 29h 46m | 1,547 km | +2h 03m | 8% | adds 3h 35m · 31 |
| 36Sir Sayyed Express 36DN | 13:30 | 12:47 +1d | 23h 17m | not measured yet | — | — | no data |
| 48Rehman Baba Express 48DN | 14:40 | 15:41 +1d | 25h 01m | 1,885 km | +2h 18m | 13% | adds 3h 53m · 34 |
| 12Hazara Express 12DN | 17:10 | 23:22 +1d | 30h 12m | 1,497 km | +1h 21m | 10% | adds 1h 42m · 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 ڈائون01:50 +1d→04:08 +2d26h 18m6% on time · +2h 09mno data over this leg
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون06:00→07:42 +1d25h 42m6% on time · +1h 05mno data over this leg
- Tezgam 8DN8تیزگام 8 ڈاؤن08:00→09:15 +1d25h 15m18% on time · +52 minno data over this leg
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون12:30→18:16 +1d29h 46m8% on time · +2h 03madds 3h 35m over this leg · 31 runs
- Sir Sayyed Express 36DN36سر سید ایکپریس 36 ڈاؤن13:30→12:47 +1d23h 17mno delay figure yetno data over this leg
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن14:40→15:41 +1d25h 01m13% on time · +2h 18madds 3h 53m over this leg · 34 runs
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن17:10→23:22 +1d30h 12m10% on time · +1h 21madds 1h 42m over this leg · 23 runs
Travelling the other way? Landhi Jn. to Rawalpindi trains →
Common questions
How many trains run from Rawalpindi to Landhi Jn.?
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 Rawalpindi to Landhi Jn.?
Sir Sayyed Express 36DN, booked at 23h 17m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Rawalpindi to Landhi Jn. is most likely to be on time?
Tezgam 8DN has the best recorded punctuality of the services we hold enough history for: 18% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 52 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 6 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Rawalpindi to Landhi Jn.?
Yes. All 7 scheduled services are booked to arrive on a later day than they depart: Khyber Mail 2DN, Pakistan Express 46DN, Tezgam 8DN, Awam Express 14DN and others.
Do trains lose time between Rawalpindi and Landhi Jn.?
Typically yes. Rehman Baba Express 48DN adds about 3h 53m to its delay over this leg, measured across 34 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 Rawalpindi to Landhi Jn. by train?
It is between 1,474 and 1,885 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 6 of the 7 services; the rest of the track on this route has not been traced yet.
Are these Rawalpindi to Landhi 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.