Attock City Jn to Karachi Cantt
Rehman Baba Express 48DN — within 15 minutes of the scheduled time 13% of the time, typically 138 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 Attock City Jn to Karachi Cantt it typically adds 3h 18m, from 34 recorded runs. At Karachi Cantt it has typically arrived 218 minutes late, from 42 recorded runs.
Every train, compared
3 of 4 with 7+ daysOver this leg is the CHANGE in a train's delay between Attock City Jn 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 Attock City Jn — no booked arrival at Attock City Jn to measure from at all. Figures cover runs recorded between 31 July 2026 and 6 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 14Awam Express 14DN | 10:20 | 19:25 +1d | 33h 05m | 1,653 km | +2h 03m | 8% | adds 3h 10m · 29 |
| 48Rehman Baba Express 48DN | 12:46 | 16:55 +1d | 28h 09m | 1,986 km | +2h 18m | 13% | adds 3h 18m · 34 |
| 20Khushhal Khan Khatak Express 20Dn | 18:20 | 05:30 +2d | 35h 10m | not measured yet | — | — | no data |
| 2Khyber Mail 2DN | 23:45 | 05:15 +2d | 29h 30m | 1,647 km | +2h 09m | 6% | 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.
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون10:20→19:25 +1d33h 05m8% on time · +2h 03madds 3h 10m over this leg · 29 runs
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن12:46→16:55 +1d28h 09m13% on time · +2h 18madds 3h 18m over this leg · 34 runs
- Khushhal Khan Khatak Express 20Dn20خوشحال خان خٹک ایکسپریس18:20→05:30 +2d35h 10mno delay figure yetno data over this leg
- Khyber Mail 2DN2خیبر میل 2 ڈائون23:45→05:15 +2d29h 30m6% on time · +2h 09mno data over this leg
Travelling the other way? Karachi Cantt to Attock City Jn trains →
Common questions
How many trains run from Attock City Jn to Karachi Cantt?
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 Attock City Jn to Karachi Cantt?
Rehman Baba Express 48DN, booked at 28h 09m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Attock City Jn to Karachi Cantt is most likely to be on time?
Rehman Baba Express 48DN has the best recorded punctuality of the services we hold enough history for: 13% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 2h 18m. That is its record across every stop of its full journey, not this leg alone: over just Attock City Jn to Karachi Cantt it typically adds 3h 18m, from 34 recorded runs. 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 Attock City Jn to Karachi Cantt?
Yes. All 4 scheduled services are booked to arrive on a later day than they depart: Awam Express 14DN, Rehman Baba Express 48DN, Khushhal Khan Khatak Express 20Dn, Khyber Mail 2DN.
Do trains lose time between Attock City Jn and Karachi Cantt?
Typically yes. Rehman Baba Express 48DN adds about 3h 18m 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 Attock City Jn to Karachi Cantt by train?
It is between 1,647 and 1,986 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 Attock City Jn 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.