Karachi Cantt to Jhelum
Hazara Express 11UP — within 15 minutes of the scheduled time 22% of the time, typically 53 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 Karachi Cantt to Jhelum it typically adds 1h 54m, from 25 recorded runs. At Jhelum it has typically arrived 136 minutes late, from 24 recorded runs.
Every train, compared
5 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Karachi Cantt and Jhelum 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 Karachi Cantt — no booked arrival at Karachi Cantt to measure from at all. Figures cover runs recorded between 31 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 |
|---|---|---|---|---|---|---|---|
| 11Hazara Express 11UP | 07:00 | 11:12 +1d | 28h 12m | 1,394 km | +53 min | 22% | adds 1h 54m · 25 |
| 13Awam Express 13UP | 07:30 | 10:58 +1d | 27h 28m | 1,445 km | +1h 43m | 6% | no data |
| 45Pakistan Express 45UP | 14:00 | 14:43 +1d | 24h 43m | 1,373 km | +2h 15m | 3% | no data |
| 7Tezgam 7UP | 17:30 | 17:31 +1d | 24h 01m | 1,424 km | +1h 57m | 5% | no data |
| 35Sir Sayyed Express 35UP | 21:00 | 19:11 +1d | 22h 11m | not measured yet | — | — | no data |
| 1Khyber Mail 1UP | 22:15 | 23:04 +1d | 24h 49m | 1,444 km | +1h 45m | 9% | no data |
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.
- Hazara Express 11UP11ہزارا ایکسپریس 11 اپ07:00→11:12 +1d28h 12m22% on time · +53 minadds 1h 54m over this leg · 25 runs
- Awam Express 13UP13عوام ایکسپریس 13 اپ07:30→10:58 +1d27h 28m6% on time · +1h 43mno data over this leg
- Pakistan Express 45UP45پاکستان ایکسپریس 45 اپ14:00→14:43 +1d24h 43m3% on time · +2h 15mno data over this leg
- Tezgam 7UP7تيزگام 7 اپ17:30→17:31 +1d24h 01m5% on time · +1h 57mno data over this leg
- Sir Sayyed Express 35UP35سر سید ایکپریس 35اپ21:00→19:11 +1d22h 11mno delay figure yetno data over this leg
- Khyber Mail 1UP1خیبر میل 1 اپ22:15→23:04 +1d24h 49m9% on time · +1h 45mno data over this leg
Travelling the other way? Jhelum to Karachi Cantt trains →
Common questions
How many trains run from Karachi Cantt to Jhelum?
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 Karachi Cantt to Jhelum?
Sir Sayyed Express 35UP, booked at 22h 11m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Karachi Cantt to Jhelum is most likely to be on time?
Hazara Express 11UP has the best recorded punctuality of the services we hold enough history for: 22% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 53 min. That is its record across every stop of its full journey, not this leg alone: over just Karachi Cantt to Jhelum it typically adds 1h 54m, from 25 recorded runs. 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 Karachi Cantt to Jhelum?
Yes. All 6 scheduled services are booked to arrive on a later day than they depart: Hazara Express 11UP, Awam Express 13UP, Pakistan Express 45UP, Tezgam 7UP and others.
Do trains lose time between Karachi Cantt and Jhelum?
Typically yes. Hazara Express 11UP adds about 1h 54m to its delay over this leg, measured across 25 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 Karachi Cantt to Jhelum by train?
It is between 1,373 and 1,445 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 Karachi Cantt to Jhelum 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.