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. That is its whole-journey record, a different promise from this leg alone: over just Jhelum to Karachi Cantt it typically adds 2h 26m, from 20 recorded runs. At Karachi Cantt it has typically arrived 184 minutes late, from 20 recorded runs.
Every train, compared
5 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Jhelum and Karachi Cantt 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 Jhelum — no booked arrival at Jhelum to measure from at all. Figures cover runs recorded between 30 July 2026 and 3 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 | 03:50 +1d | 05:15 +2d | 25h 25m | 1,445 km | +2h 09m | 6% | no data |
| 46Pakistan Express 46DN | 08:02 | 08:45 +1d | 24h 43m | 1,373 km | +1h 05m | 6% | adds 3h 09m · 13 |
| 8Tezgam 8DN | 10:08 | 10:30 +1d | 24h 22m | 1,426 km | +52 min | 18% | adds 2h 26m · 20 |
| 14Awam Express 14DN | 14:46 | 19:25 +1d | 28h 39m | 1,445 km | +2h 03m | 8% | adds 2h 03m · 30 |
| 36Sir Sayyed Express 36DN | 15:25 | 14:10 +1d | 22h 45m | not measured yet | — | — | no data |
| 12Hazara Express 12DN | 19:37 | 00:30 +2d | 28h 53m | 1,394 km | +1h 21m | 10% | adds 57 min · 21 |
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 ڈائون03:50 +1d→05:15 +2d25h 25m6% on time · +2h 09mno data over this leg
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون08:02→08:45 +1d24h 43m6% on time · +1h 05madds 3h 09m over this leg · 13 runs
- Tezgam 8DN8تیزگام 8 ڈاؤن10:08→10:30 +1d24h 22m18% on time · +52 minadds 2h 26m over this leg · 20 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون14:46→19:25 +1d28h 39m8% on time · +2h 03madds 2h 03m over this leg · 30 runs
- Sir Sayyed Express 36DN36سر سید ایکپریس 36 ڈاؤن15:25→14:10 +1d22h 45mno delay figure yetno data over this leg
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن19:37→00:30 +2d28h 53m10% on time · +1h 21madds 57 min over this leg · 21 runs
Travelling the other way? Karachi Cantt to Jhelum trains →
Common questions
How many trains run from Jhelum to Karachi Cantt?
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 Jhelum to Karachi Cantt?
Sir Sayyed Express 36DN, booked at 22h 45m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Jhelum to Karachi Cantt 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. 5 of 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Jhelum to Karachi Cantt?
Yes. All 6 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 Jhelum and Karachi Cantt?
Typically yes. Pakistan Express 46DN adds about 3h 09m to its delay over this leg, measured across 13 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 Jhelum to Karachi Cantt 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 Jhelum to Karachi Cantt 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.