Lala Musa Jn. to Malakwal Jn
Chanab Express 136dn — within 15 minutes of the scheduled time 41% of the time, typically 18 minutes late, over 8 days of recorded runs across every stop of its full journey, not this segment alone. At Malakwal Jn it has typically arrived 14 minutes late, from 21 recorded runs.
Every train, compared
3 of 4 with 7+ daysOver this leg is the CHANGE in a train's delay between Lala Musa Jn. and Malakwal 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 Lala Musa Jn. — no booked arrival at Lala Musa Jn. to measure from at all. Figures cover runs recorded between 30 July 2026 and 5 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 278Sargodha Shuttle-S2dn | 06:00 | 07:45 | 1h 45m | 76 km | — | — | no data |
| 18Millat Express 18DN | 10:30 | 12:00 | 1h 30m | 74 km | +2h 37m | 10% | no data |
| 136Chanab Express 136dn | 15:45 | 17:30 | 1h 45m | not measured yet | +18 min | 41% | no data |
| 12Hazara Express 12DN | 20:55 | 22:20 | 1h 25m | 73 km | +1h 17m | 10% | adds 6 min · 24 |
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.
- Sargodha Shuttle-S2dn278پنڈ دادنخان شٹل 6 ڈاؤن06:00→07:451h 45mno delay figure yetno data over this leg
- Millat Express 18DN18ملت ایکسپریس 18 ڈائون10:30→12:001h 30m10% on time · +2h 37mno data over this leg
- Chanab Express 136dn136چناب ایکسپریس 136 ڈاؤن15:45→17:301h 45m41% on time · +18 minno data over this leg
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن20:55→22:201h 25m10% on time · +1h 17madds 6 min over this leg · 24 runs
Travelling the other way? Malakwal Jn to Lala Musa Jn. trains →
Common questions
How many trains run from Lala Musa Jn. to Malakwal Jn?
4 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Lala Musa Jn. to Malakwal Jn?
Hazara Express 12DN, booked at 1h 25m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Lala Musa Jn. to Malakwal Jn is most likely to be on time?
Chanab Express 136dn 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 18 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 3 of 4 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Lala Musa Jn. to Malakwal 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 Lala Musa Jn. and Malakwal Jn?
Typically yes. Hazara Express 12DN adds about 6 min to its delay over this leg, measured across 24 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 Lala Musa Jn. to Malakwal Jn by train?
It is between 73 and 76 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 3 of the 4 services; the rest of the track on this route has not been traced yet.
Are these Lala Musa Jn. to Malakwal 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.