Toba Tek Singh to Karachi Cantt
Shalimar Express 28DN — within 15 minutes of the scheduled time 44% of the time, typically 22 minutes late, over 10 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
4 of 5 with 7+ daysOver this leg is the CHANGE in a train's delay between Toba Tek Singh 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 Toba Tek Singh — no booked arrival at Toba Tek Singh 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 |
|---|---|---|---|---|---|---|---|
| 28Shalimar Express 28DN | 10:55 | 02:55 +1d | 16h | not measured yet | +22 min | 44% | no data |
| 46Pakistan Express 46DN | 14:40 | 08:45 +1d | 18h 05m | 1,071 km | +1h 02m | 5% | adds 2h 18m · 23 |
| 42Karakoram Express 42DN | 18:32 | 10:45 +1d | 16h 13m | not measured yet | — | — | no data |
| 18Millat Express 18DN | 19:00 | 12:40 +1d | 17h 40m | 1,028 km | +2h 37m | 10% | adds 2h 09m · 23 |
| 48Rehman Baba Express 48DN | 22:42 | 16:55 +1d | 18h 13m | 1,072 km | +2h 20m | 13% | adds 2h 09m · 35 |
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.
- Shalimar Express 28DN28شالیمار ایکسپریس 28 ڈائون10:55→02:55 +1d16h44% on time · +22 minno data over this leg
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون14:40→08:45 +1d18h 05m5% on time · +1h 02madds 2h 18m over this leg · 23 runs
- Karakoram Express 42DN42قراقرم ایکسپریس 42 ڈائون18:32→10:45 +1d16h 13mno delay figure yetno data over this leg
- Millat Express 18DN18ملت ایکسپریس 18 ڈائون19:00→12:40 +1d17h 40m10% on time · +2h 37madds 2h 09m over this leg · 23 runs
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن22:42→16:55 +1d18h 13m13% on time · +2h 20madds 2h 09m over this leg · 35 runs
Travelling the other way? Karachi Cantt to Toba Tek Singh trains →
Common questions
How many trains run from Toba Tek Singh 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 Toba Tek Singh to Karachi Cantt?
Shalimar Express 28DN, booked at 16h for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Toba Tek Singh 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. 4 of 5 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Toba Tek Singh to Karachi Cantt?
Yes. All 5 scheduled services are booked to arrive on a later day than they depart: Shalimar Express 28DN, Pakistan Express 46DN, Karakoram Express 42DN, Millat Express 18DN and others.
Do trains lose time between Toba Tek Singh and Karachi Cantt?
Typically yes. Pakistan Express 46DN adds about 2h 18m 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 Toba Tek Singh to Karachi Cantt by train?
It is between 1,028 and 1,072 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 Toba Tek Singh 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.