Karachi Cantt to Raiwind Jn.
Pak Business 33UP — within 15 minutes of the scheduled time 10% of the time, typically 121 minutes late, over 9 days of recorded runs across every stop of its full journey, not this segment alone. At Raiwind Jn. it has typically arrived 201 minutes late, from 45 recorded runs.
Every train, compared
7 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Karachi Cantt and Raiwind Jn. 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 29 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 13Awam Express 13UP | 07:30 | 06:15 +1d | 22h 45m | 1,228 km | +1h 42m | 6% | no data |
| 9Allama Iqbal Express 9UP | 15:30 | 11:25 +1d | 19h 55m | 1,178 km | +2h 52m | 5% | no data |
| 33Pak Business 33UP | 16:00 | 09:15 +1d | 17h 15m | 1,173 km | +2h 01m | 10% | no data |
| 7Tezgam 7UP | 17:30 | 13:00 +1d | 19h 30m | 1,215 km | +1h 59m | 5% | no data |
| 15Karachi Express 15UP | 18:00 | 11:50 +1d | 17h 50m | 1,221 km | +1h 45m | 10% | no data |
| 37Fareed Express 37UP | 19:50 | 21:10 +1d | 25h 20m | 1,224 km | +1h 19m | 8% | adds 1h 54m · 26 |
| 1Khyber Mail 1UP | 22:15 | 18:10 +1d | 19h 55m | 1,226 km | +1h 39m | 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.
- Awam Express 13UP13عوام ایکسپریس 13 اپ07:30→06:15 +1d22h 45m6% on time · +1h 42mno data over this leg
- Allama Iqbal Express 9UP9علامہ اقبال ایکسپریس 9 اپ15:30→11:25 +1d19h 55m5% on time · +2h 52mno data over this leg
- Pak Business 33UP33پاک بزنس 33 اپ16:00→09:15 +1d17h 15m10% on time · +2h 01mno data over this leg
- Tezgam 7UP7تيزگام 7 اپ17:30→13:00 +1d19h 30m5% on time · +1h 59mno data over this leg
- Karachi Express 15UP15کراچی ایکسپریس 15 اپ18:00→11:50 +1d17h 50m10% on time · +1h 45mno data over this leg
- Fareed Express 37UP37فرید ایکسپریس 37 اپ19:50→21:10 +1d25h 20m8% on time · +1h 19madds 1h 54m over this leg · 26 runs
- Khyber Mail 1UP1خیبر میل 1 اپ22:15→18:10 +1d19h 55m9% on time · +1h 39mno data over this leg
Travelling the other way? Raiwind Jn. to Karachi Cantt trains →
Common questions
How many trains run from Karachi Cantt to Raiwind Jn.?
7 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 Raiwind Jn.?
Pak Business 33UP, booked at 17h 15m 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 Raiwind Jn. is most likely to be on time?
Pak Business 33UP has the best recorded punctuality of the services we hold enough history for: 10% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 2h 01m. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 7 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Karachi Cantt to Raiwind Jn.?
Yes. All 7 scheduled services are booked to arrive on a later day than they depart: Awam Express 13UP, Allama Iqbal Express 9UP, Pak Business 33UP, Tezgam 7UP and others.
Do trains lose time between Karachi Cantt and Raiwind Jn.?
Typically yes. Fareed Express 37UP adds about 1h 54m to its delay over this leg, measured across 26 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 Raiwind Jn. by train?
It is between 1,173 and 1,228 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.
Are these Karachi Cantt to Raiwind Jn. 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.