Sukkur Express 146DN — within 15 minutes of the scheduled time 39% of the time, typically 19 minutes late, over 9 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 Padidan to Karachi Cantt it typically adds 58 min, from 23 recorded runs. At Karachi Cantt it has typically arrived 80 minutes late, from 29 recorded runs.
Every train, compared
5 of 5 with 7+ daysOver this leg is the CHANGE in a train's delay between Padidan 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 Padidan — no booked arrival at Padidan 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 |
|---|---|---|---|---|---|---|---|
| 38Fareed Express 38DN | 00:41 +1d | 07:55 +1d | 7h 14m | not measured yet | +44 min | 14% | adds 6 min · 28 |
| 46Pakistan Express 46DN | 02:05 +1d | 08:45 +1d | 6h 40m | 348 km | +1h 02m | 5% | adds 33 min · 21 |
| 14Awam Express 14DN | 11:29 +1d | 19:25 +1d | 7h 56m | 350 km | +2h 09m | 8% | makes up 2 min · 30 |
| 12Hazara Express 12DN | 17:22 +1d | 00:30 +2d | 7h 08m | 351 km | +1h 17m | 10% | makes up 8 min · 31 |
| 146Sukkur Express 146DN | 23:49 | 07:35 +1d | 7h 46m | not measured yet | +19 min | 39% | adds 58 min · 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.
- Fareed Express 38DN38فرید ایکسپریس 38 ڈائون00:41 +1d→07:55 +1d7h 14m14% on time · +44 minadds 6 min over this leg · 28 runs
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون02:05 +1d→08:45 +1d6h 40m5% on time · +1h 02madds 33 min over this leg · 21 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون11:29 +1d→19:25 +1d7h 56m8% on time · +2h 09mmakes up 2 min over this leg · 30 runs
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن17:22 +1d→00:30 +2d7h 08m10% on time · +1h 17mmakes up 8 min over this leg · 31 runs
- Sukkur Express 146DN146سکھر ایکسپریس146ڈاؤن23:49→07:35 +1d7h 46m39% on time · +19 minadds 58 min over this leg · 23 runs
Travelling the other way? Karachi Cantt to Padidan trains →
Common questions
How many trains run from Padidan to Karachi Cantt?
5 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Padidan to Karachi Cantt?
Pakistan Express 46DN, booked at 6h 40m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Padidan to Karachi Cantt is most likely to be on time?
Sukkur Express 146DN has the best recorded punctuality of the services we hold enough history for: 39% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 19 min. That is its record across every stop of its full journey, not this leg alone: over just Padidan to Karachi Cantt it typically adds 58 min, from 23 recorded runs. Measured from recorded runs, not from the timetable. 5 of 5 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Padidan to Karachi Cantt?
Yes. 2 of the 5 scheduled services are booked to arrive on a later day than they depart: Hazara Express 12DN, Sukkur Express 146DN.
Do trains lose time between Padidan and Karachi Cantt?
Typically yes. Sukkur Express 146DN adds about 58 min to its delay over this leg, measured across 23 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 Padidan to Karachi Cantt by train?
It is between 348 and 351 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 5 services; the rest of the track on this route has not been traced yet.
Are these Padidan 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.