latetrains.pkLate, on record44 live
Trains/Lahore–Karachi/Karachi Express 16DN

16 Karachi Express 16DN کراچی ایکسپریس 16 ڈائون

Kitni late hoti hai? Typical delay, on-time record aur station timings.
LAHOREKARACHILAHORE
Down direction · returnsلاہور جنکشن ۔ کراچی کينٹ ۔ لاہور جنکشن
In service since 1943ExpressLast seen 9 October 202671 days trackedTrack it live →
Live running status — right nowLive · 12 sec · official GPS

Running 59 min late — heading for Okara, due 20:45 (operator's estimate), 91 km/h. Last crossed Raiwind Jn..

How late is it, usually?

median per recorded stop arrival

Every figure here is a median, not an average: why we publish a median, not an average. What counts as on time, and why some figures here are blank, is set out in what on time means here, and every threshold behind it.

At Karachi Cantt+3h 36mmedian of 34 recorded arrivals · 31 Jul – 8 Oct 2026
Typical delay, any stop+1h 59mat a station this train calls at, not necessarily where you board · last 28 days
On time (within 15 min)17% of recorded stop arrivals
Bad day (90th percentile)+3h 46mworse than nine tenths of recorded stop arrivals

9 days of recorded arrivals.

Over 34 recorded arrivals (31 Jul – 8 Oct 2026), Karachi Express 16DN has typically reached Karachi Cantt around 17:11 the day after it leaves — on the worst one run in ten, past 19:22 the day after it leaves, at Karachi Cantt itself. Today's run: track it live →

The “At Karachi Cantt” tile above is the arrival at the end of the run; “Typical delay, any stop” averages every stop including the earlier ones, so it usually reads smaller. Where the time goes, below, shows every stop we have recorded.

How long does it take?

scheduled vs recorded

Scheduled 19h 35m — Lahore Jn. to Karachi Cantt. Typically 23h 11m, 3h 36m longer.

Timetable: out 18:00, in at 13:35 the next day — one night on board.

What these figures cover
  • Scheduled — the current timetable, Lahore Jn. 18:00 to Karachi Cantt 13:35 the next day
  • Typical journey — from the scheduled departure to the recorded arrival at Karachi Cantt; the median of 34 runs
  • Bad day — 25h 22m at the 90th percentile: nine runs in ten come in under it
  • Keyline — the scheduled time. The solid bar is the typical journey, the faint bar behind it the bad day.
  • Recorded arrivals: 31 July to 8 October 2026.
  • End to end. For a shorter leg, the stop times are in the timetable below.

Which day is worst?

mean minutes late per recorded arrival, 8-week window
Mon+2h 12m · 5 runs
Tue+3h 09m · 5 runs
Wed+1h 42m · 5 runs
Thu+2h 02m · 4 runs
Fri+3h 35m · 5 runs
Sat+2h 54m · 4 runs
Sun+3h · 4 runs

This is a mean over an 8-week window, not the median (typical) figure above — the two are not directly comparable.

Where the time goes

most of it lost after Lahore Jn.

Leaves Lahore Jn. 5 min early · reaches Karachi Cantt +3h 36m — +3h 41m lost along the way.

  1. Lahore Jn.18:00لاہور جنکشن5 min early
  2. Raiwind Jn.18:40راۓوِنڈ جنکشن+1h 58m
  3. Sahiwal20:28ساہِيوال+1h 56m
  4. Khanewal Jn22:00خانیوال+1h 58m
  5. Multan Cantt23:00ملتان کینٹ+2h 09m
  6. Bahawalpur00:20بہاولپور+2h 24m
  7. Rohri Jn.05:25روہڑی جنکشن+2h 37m
  8. Nawabshah Jn.08:12نوابشاہ جنکشن+3h 07m
  9. Hyderabad Jn10:20حیدرآباد جنکشن+3h 08m
  10. Landhi Jn.12:29لانڈھی جنکشن+3h 58m
  11. Drigh Road13:07ڈرگ روڈ+3h 44m
  12. Karachi Cantt13:35کراچی کينٹ+3h 36m

Where it stands longest past the timetableshortest to longest recorded

  1. Hyderabad Jnscheduled 5 min8–42 min
  2. Rohri Jn.scheduled 25 min24 min–1h 13m
  3. Khanewal Jnscheduled 5 min5 min–1h 27m
  4. Multan Canttscheduled 20 min11 min–1h 33m
  5. Nawabshah Jn.scheduled 2 min4–13 min
What the marks mean
  • Solid bar — the typical delay at that stop (median of recorded arrivals)
  • Faint bar behind — the bad day (90th percentile): worse than nine tenths of recorded arrivals here
  • No faint bar — fewer than 7 recorded arrivals at that stop, too thin for a 90th percentile. The solid bar can still show: it needs only 3.
  • — (no solid bar either) — fewer than 3 recorded runs at that stop
  • A negative figure means the train typically ran early at that stop, not late
  • Band — the shortest and the longest stand recorded at that stop. The train has left as early as the first figure.
  • Keyline — the scheduled stop, arrival to departure on the timetable below.
  • Why a train stands is not recorded — a crossing, a loco change and a red signal all look the same on the clock.
  • The five stops that stand longest past the timetable, not every stop — most routes have more. A stop qualifies with 7 or more runs timed in and out, and is skipped where the timetable books no stop, books one over an hour, or where any recorded stand ran past three hours.
  • Most time is lost between Lahore Jn. and Raiwind Jn. (+2h 03m)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 8 October 2026 run

The second time in a cell is what actually happened on the 8 October 2026 run.

#StationArrivalDeparture
1Lahore Jn.—18:00
2Raiwind Jn.18:35 → 18:59·PR18:40
3Sahiwal20:26 → 20:33·PR20:28 → 20:39
4Khanewal Jn21:55 → 21:55·PR22:00 → 22:03
5Multan Cantt22:40 → 23:14·PR23:00
6Bahawalpur00:16 +1d → 00:19·PR00:20 +1d → 00:25
7Rohri Jn.05:00 +1d → 06:07·PR05:25 +1d → 06:19
8Nawabshah Jn.08:10 +1d → 09:20·PR08:12 +1d → 09:28
9Hyderabad Jn10:15 +1d → 11:31·PR10:20 +1d → 11:45
10Landhi Jn.12:27 +1d → 14:26·PR12:29 +1d → 14:30
11Drigh Road13:05 +1d → 14:48·PR13:07 +1d → 14:51
12Karachi Cantt13:35 +1d → 15:20— → 15:23
What the marks mean
  • → 21:28 — actual time on the 8 October 2026 run
  • ·PR — Pakistan Railways' own record; unmarked is from the train's GPS
  • +1d — the stop falls on a later day of the train's own run, counting from the day it starts. It is not a date.
  • Blank — not recorded

A full recorded run: 21 August 2026 →

Station by station, last 5 days

45 arrivals recorded

One mark per day, newest first.

Days shownFri9 OctThu8 OctWed7 OctTue6 OctMon5 Oct

A run’s GPS trail is decoded after the journey completes — recent days may link later.

  • 2Raiwind Jn.scheduled 18:35+43m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct19:30+50mPakistan Railways
    Thu 8 Oct18:59+20mPakistan Railways
    Wed 7 Octarrived, time not recorded+20mPakistan Railways
    Tue 6 Oct21:17+2h38Pakistan Railways
    Mon 5 Oct19:23+43mPakistan Railways

    Seen on 5 of 5 days, ranging +20m to +2h38. Every train at Raiwind Jn. →

  • 3Sahiwalscheduled 20:26+25m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct20:33+5mPakistan Railways
    Wed 7 Oct20:28+2mPakistan Railways
    Tue 6 Oct22:55+2h28Pakistan Railways
    Mon 5 Oct21:12+44mPakistan Railways

    Seen on 4 of 5 days, ranging +2m to +2h28. Every train at Sahiwal →

  • 4Khanewal Jnscheduled 21:55+22m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct21:555m earlyPakistan Railways
    Wed 7 Oct21:536m earlyPakistan Railways
    Tue 6 Oct00:20+2h25Pakistan Railways
    Mon 5 Oct22:49+49mPakistan Railways

    Seen on 4 of 5 days, ranging 6m early to +2h25. Every train at Khanewal Jn →

  • 5Multan Canttscheduled 22:40+40m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct23:14+14mPakistan Railways
    Wed 7 Oct23:09+3mPakistan Railways
    Tue 6 Oct01:06+2h26Pakistan Railways
    Mon 5 Oct00:06+1h06Pakistan Railways

    Seen on 4 of 5 days, ranging +3m to +2h26. Every train at Multan Cantt →

  • 6Bahawalpurscheduled 00:16+31m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct00:19+4mPakistan Railways
    Wed 7 Oct00:0811m earlyPakistan Railways
    Tue 6 Oct02:42+2h22Pakistan Railways
    Mon 5 Oct01:18+58mPakistan Railways

    Seen on 4 of 5 days, ranging 11m early to +2h22. Every train at Bahawalpur →

  • 7Rohri Jn.scheduled 05:00+44m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct06:07+42mPakistan Railways
    Wed 7 Oct05:34+9mPakistan Railways
    Tue 6 Oct07:30+2h05Pakistan Railways
    Mon 5 Oct06:09+45mPakistan Railways

    Seen on 4 of 5 days, ranging +9m to +2h05. Every train at Rohri Jn. →

  • 8Nawabshah Jn.scheduled 08:10+1h534 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct09:20+1h10Pakistan Railways
    Wed 7 Oct10:29+2h18Pakistan Railways
    Tue 6 Oct10:46+2h35Pakistan Railways
    Mon 5 Oct09:40+1h28Pakistan Railways

    Seen on 4 of 5 days, ranging +1h10 to +2h35. Every train at Nawabshah Jn. →

  • 9Hyderabad Jnscheduled 10:15+2h144 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct11:31+1h11Pakistan Railways
    Wed 7 Oct12:40+2h21Pakistan Railways
    Tue 6 Oct12:51+2h32Pakistan Railways
    Mon 5 Octarrived, time not recorded+2h07Pakistan Railways

    Seen on 4 of 5 days, ranging +1h11 to +2h32. Every train at Hyderabad Jn →

  • 10Landhi Jn.scheduled 12:27+2h524 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct14:26+1h57Pakistan Railways
    Wed 7 Oct15:58+3h29Pakistan Railways
    Tue 6 Oct15:48+3h19Pakistan Railways
    Mon 5 Oct14:54+2h25Pakistan Railways

    Seen on 4 of 5 days, ranging +1h57 to +3h29. Every train at Landhi Jn. →

  • 11Drigh Roadscheduled 13:05+2h354 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct14:48+1h41Pakistan Railways
    Wed 7 Oct16:18+3h11Pakistan Railways
    Tue 6 Oct16:09+3h03Pakistan Railways
    Mon 5 Oct15:12+2h06Pakistan Railways

    Seen on 4 of 5 days, ranging +1h41 to +3h11. Every train at Drigh Road →

  • 12Karachi Canttscheduled 13:35+2h354 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct15:20+1h45Train GPS
    Wed 7 Oct17:01+3h26Train GPS
    Tue 6 Oct16:44+3h10Train GPS
    Mon 5 Oct15:34+1h59Train GPS

    Seen on 4 of 5 days, ranging +1h45 to +3h26. Every train at Karachi Cantt →

What the marks mean
  • Tap a station — each day’s arrival, delay and recorder
  • Green — within 15 minutes of the scheduled time
  • Amber — 16 to 45 minutes late
  • Red — over 45 minutes late
  • Hollow — not recorded that day
  • Grey — arrived, no delay figure
  • Dash (—) — no delay figure for this stop yet
  • Pakistan Railways — its own arrival record; Train GPS — measured from the train’s position
  • The starting station is not listed — a train does not arrive where it begins.
Karachi Express 16DN
Karachiexp · CC BY-SA 3.0

Common questions

Is Karachi Express 16DN usually late?

Typically 216 minutes late arriving at Karachi Cantt, measured across 34 recorded arrivals (31 Jul – 8 Oct 2026). That is the median, so half its runs were better than that and half were worse. It is what we recorded happening, not what the timetable books.

How late is Karachi Express 16DN on a bad day?

On the worst one run in ten, 347 minutes late into Karachi Cantt, against a typical 216 minutes late. Both come from the same 34 recorded arrivals. A bad day is not the worst day we have ever seen; it is the level one run in ten reaches or passes.

What time does Karachi Express 16DN leave Lahore Jn.?

18:00, on the current published timetable. It is booked into Karachi Cantt at 13:35, the day after it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does Karachi Express 16DN take from Lahore Jn. to Karachi Cantt?

19h 35m on the timetable. In practice a typical run has taken 23h 11m, measured from recorded arrivals at Karachi Cantt.

How many stops does Karachi Express 16DN make?

12 on the current published timetable, from Lahore Jn. to Karachi Cantt. The full stop list, with the times booked at each one, is in the timetable on this page. Not every stop is recorded on every run: we publish arrivals we actually observed rather than filling the gaps.

Where is Karachi Express 16DN right now?

The live tracker for this train shows its last reported position and how late it was running at its most recent recorded stop. Position comes from the operator's own feed. When a train is not reporting we say so rather than estimating where it might be.

All Lahore–Karachi trains →

Service history (first year, operating eras) is drawn from Wikipedia's List of Pakistan Railways trains, retrieved 15 August 2026, matched on train number. Further reading: the train's own Wikipedia article.