Khanewal Jn to Karachi Cantt
Shalimar Express 28DN — within 15 minutes of the scheduled time 44% of the time, typically 22 minutes late, over 11 days of recorded runs across every stop of its full journey, not this segment alone. At Karachi Cantt it has typically arrived 62 minutes late, from 27 recorded runs.
Every train, compared
12 of 15 with 7+ daysOver this leg is the CHANGE in a train's delay between Khanewal 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 Khanewal Jn — no booked arrival at Khanewal Jn to measure from at all. Figures cover runs recorded between 30 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 |
|---|---|---|---|---|---|---|---|
| 6Green Line 6DN | 00:25 +1d | 14:20 +1d | 13h 55m | 931 km | +43 min | 37% | adds 1h 47m · 35 |
| 48Rehman Baba Express 48DN | 00:27 +1d | 16:55 +1d | 16h 28m | 979 km | +2h 18m | 13% | adds 2h 37m · 35 |
| 44Shah Hussain Express 44DN | 02:10 +1d | 16:00 +1d | 13h 50m | not measured yet | — | — | no data |
| 12Hazara Express 12DN | 06:00 +1d | 00:30 +2d | 18h 30m | 982 km | +1h 21m | 10% | adds 28 min · 23 |
| 2Khyber Mail 2DN | 12:40 +1d | 05:15 +2d | 16h 35m | 985 km | +2h 09m | 6% | adds 1h 48m · 10 |
| 46Pakistan Express 46DN | 16:35 | 08:45 +1d | 16h 10m | 977 km | +1h 05m | 6% | adds 2h 27m · 21 |
| 10Allama Iqbal Express 10DN | 17:25 | 09:15 +1d | 15h 50m | 937 km | +54 min | 25% | adds 2h 05m · 19 |
| 8Tezgam 8DN | 18:15 | 10:30 +1d | 16h 15m | 975 km | +52 min | 18% | adds 1h 57m · 20 |
| 42Karakoram Express 42DN | 20:25 | 10:45 +1d | 14h 20m | not measured yet | — | — | adds 2h 33m · 18 |
| 34Pak Business 34DN | 20:50 | 11:30 +1d | 14h 40m | 930 km | +59 min | 20% | adds 2h 32m · 22 |
| 18Millat Express 18DN | 21:05 | 12:40 +1d | 15h 35m | 935 km | +2h 36m | 10% | adds 2h 39m · 24 |
| 16Karachi Express 16DN | 22:00 | 13:35 +1d | 15h 35m | 978 km | +1h 59m | 17% | adds 1h 54m · 32 |
| 36Sir Sayyed Express 36DN | 23:25 | 14:10 +1d | 14h 45m | not measured yet | — | — | no data |
| 14Awam Express 14DN | 23:50 | 19:25 +1d | 19h 35m | 985 km | +2h 03m | 8% | adds 1h 17m · 34 |
| 28Shalimar Express 28DN | — | 02:55 +1d | — | not measured yet | +22 min | 44% | 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.
- Green Line 6DN6گرين لائن 6 ڈاؤن00:25 +1d→14:20 +1d13h 55m37% on time · +43 minadds 1h 47m over this leg · 35 runs
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن00:27 +1d→16:55 +1d16h 28m13% on time · +2h 18madds 2h 37m over this leg · 35 runs
- Shah Hussain Express 44DN44شاہ حسین ایکسپریس 44 ڈاؤن02:10 +1d→16:00 +1d13h 50mno delay figure yetno data over this leg
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن06:00 +1d→00:30 +2d18h 30m10% on time · +1h 21madds 28 min over this leg · 23 runs
- Khyber Mail 2DN2خیبر میل 2 ڈائون12:40 +1d→05:15 +2d16h 35m6% on time · +2h 09madds 1h 48m over this leg · 10 runs
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون16:35→08:45 +1d16h 10m6% on time · +1h 05madds 2h 27m over this leg · 21 runs
- Allama Iqbal Express 10DN10علامہ اقبال ایکسپریس 10 ڈائون17:25→09:15 +1d15h 50m25% on time · +54 minadds 2h 05m over this leg · 19 runs
- Tezgam 8DN8تیزگام 8 ڈاؤن18:15→10:30 +1d16h 15m18% on time · +52 minadds 1h 57m over this leg · 20 runs
- Karakoram Express 42DN42قراقرم ایکسپریس 42 ڈائون20:25→10:45 +1d14h 20mno delay figure yetadds 2h 33m over this leg · 18 runs
- Pak Business 34DN34پاک بزنس 34 ڈائون20:50→11:30 +1d14h 40m20% on time · +59 minadds 2h 32m over this leg · 22 runs
- Millat Express 18DN18ملت ایکسپریس 18 ڈائون21:05→12:40 +1d15h 35m10% on time · +2h 36madds 2h 39m over this leg · 24 runs
- Karachi Express 16DN16کراچی ایکسپریس 16 ڈائون22:00→13:35 +1d15h 35m17% on time · +1h 59madds 1h 54m over this leg · 32 runs
- Sir Sayyed Express 36DN36سر سید ایکپریس 36 ڈاؤن23:25→14:10 +1d14h 45mno delay figure yetno data over this leg
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون23:50→19:25 +1d19h 35m8% on time · +2h 03madds 1h 17m over this leg · 34 runs
- Shalimar Express 28DN28شالیمار ایکسپریس 28 ڈائون—→02:55 +1d—44% on time · +22 minno data over this leg
Travelling the other way? Karachi Cantt to Khanewal Jn trains →
Common questions
How many trains run from Khanewal Jn to Karachi Cantt?
15 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Khanewal Jn to Karachi Cantt?
Shah Hussain Express 44DN, booked at 13h 50m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Khanewal Jn to Karachi Cantt is most likely to be on time?
Shalimar Express 28DN has the best recorded punctuality of the services we hold enough history for: 44% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 22 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 12 of 15 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Khanewal Jn to Karachi Cantt?
Yes. 12 of the 15 scheduled services are booked to arrive on a later day than they depart: Hazara Express 12DN, Khyber Mail 2DN, Pakistan Express 46DN, Allama Iqbal Express 10DN and others.
Do trains lose time between Khanewal Jn and Karachi Cantt?
Typically yes. Millat Express 18DN adds about 2h 39m 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 Khanewal Jn to Karachi Cantt by train?
It is between 930 and 985 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 11 of the 15 services; the rest of the track on this route has not been traced yet.
Are these Khanewal 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.