latetrains.pkLate, on record44 live
Trains/Karachi–Lahore/Karachi Express 15UP

15 Karachi Express 15UP کراچی ایکسپریس 15 اپ

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

Running 40 min late — heading for Hyderabad Jn, due 21:12 (operator's estimate), 93 km/h. Last crossed Karachi Cantt.

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 Lahore Jn.+3h 08mmedian of 30 recorded arrivals · 30 Jul – 8 Oct 2026
Typical delay, any stop+1h 45mat a station this train calls at, not necessarily where you board · last 28 days
On time (within 15 min)10% of recorded stop arrivals
Bad day (90th percentile)+4h 01mworse than nine tenths of recorded stop arrivals

10 days of recorded arrivals.

Over 30 recorded arrivals (30 Jul – 8 Oct 2026), Karachi Express 15UP has typically reached Lahore Jn. around 16:08 the day after it leaves — on the worst one run in ten, past 17:51 the day after it leaves, at Lahore Jn. itself. Today's run: track it live →

The “At Lahore Jn.” 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 — Karachi Cantt to Lahore Jn.. Typically 22h 08m, 3h 08m longer.

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

What these figures cover
  • Scheduled — the current timetable, Karachi Cantt 18:00 to Lahore Jn. 13:00 the next day
  • Typical journey — from the scheduled departure to the recorded arrival at Lahore Jn.; the median of 30 runs
  • Bad day — 23h 51m 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: 30 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 36m · 5 runs
Tue+1h 31m · 5 runs
Wed+1h 44m · 5 runs
Thu+2h 36m · 4 runs
Fri+1h 53m · 5 runs
Sat+2h 38m · 4 runs
Sun+2h 24m · 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 Karachi Cantt

Leaves Karachi Cantt 27 min early · reaches Lahore Jn. +3h 08m — +3h 35m lost along the way.

  1. Karachi Cantt18:00کراچی کينٹ27 min early
  2. Hyderabad Jn20:40حیدرآباد جنکشن+1h 18m
  3. Nawabshah Jn.22:18نوابشاہ جنکشن+1h 43m
  4. Rohri Jn.01:35روہڑی جنکشن+1h 36m
  5. Bahawalpur06:32بہاولپور+2h 25m
  6. Multan Cantt08:15ملتان کینٹ+2h 17m
  7. Khanewal Jn09:00خانیوال+2h 33m
  8. Sahiwal10:25ساہِيوال+2h 40m
  9. Raiwind Jn.11:55راۓوِنڈ جنکشن+2h 48m
  10. Kot Lakhpat12:22کوٹ لکھپت+2h 56m
  11. Lahore Jn.13:00لاہور جنکشن+3h 08m

Where it stands longest past the timetableshortest to longest recorded

  1. Rohri Jn.scheduled 25 min22 min–1h 54m
  2. Multan Canttscheduled 20 min24–52 min
  3. Hyderabad Jnscheduled 8 min8–29 min
  4. Sahiwalscheduled 2 min3–15 min
  5. Nawabshah Jn.scheduled 2 min3–17 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 Karachi Cantt and Hyderabad Jn (+1h 45m)
  • 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
1Karachi Cantt18:0018:00
2Hyderabad Jn20:32 → 21:16·PR20:40 → 21:19
3Nawabshah Jn.22:16 → 00:02·PR22:18 → 00:10
4Rohri Jn.01:10 +1d → 03:12·PR01:35 +1d → 03:19
5Bahawalpur06:30 +1d → 08:40·PR06:32 +1d → 08:44
6Multan Cantt07:55 +1d → 09:52·PR08:15 +1d → 10:19
7Khanewal Jn08:55 +1d → 11:01·PR09:00 +1d → 11:07
8Sahiwal10:23 +1d → 12:26·PR10:25 +1d → 12:33
9Raiwind Jn.11:50 +1d → 14:08·PR11:55 +1d → 14:13
10Kot Lakhpat12:20 +1d → 14:41·PR12:22 +1d → 14:45
11Lahore Jn.13:00 +1d → 15:19—
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: 18 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.

  • 1Karachi Canttscheduled 18:0040m early5 days
    DayArrivedDelayRecorded by
    Fri 9 Octarrived, time not recorded26m earlyPakistan Railways
    Thu 8 Octarrived, time not recorded55m earlyPakistan Railways
    Wed 7 Octarrived, time not recorded40m earlyPakistan Railways
    Tue 6 Octarrived, time not recorded44m earlyPakistan Railways
    Mon 5 Octarrived, time not recorded31m earlyPakistan Railways

    Seen on 5 of 5 days, ranging 55m early to 26m early. Every train at Karachi Cantt →

  • 2Hyderabad Jnscheduled 20:32+55m4 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct21:16+36mPakistan Railways
    Wed 7 Oct21:53+1h13Pakistan Railways
    Tue 6 Oct21:09+30mPakistan Railways
    Mon 5 Oct22:14+1h34Pakistan Railways

    Seen on 4 of 5 days, ranging +30m to +1h34. Every train at Hyderabad Jn →

  • 3Nawabshah Jn.scheduled 22:16+1h324 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct00:02+1h45Pakistan Railways
    Wed 7 Oct23:43+1h25Pakistan Railways
    Tue 6 Oct23:00+42mPakistan Railways
    Mon 5 Oct23:56+1h39Pakistan Railways

    Seen on 4 of 5 days, ranging +42m to +1h45. Every train at Nawabshah Jn. →

  • 4Rohri Jn.scheduled 01:10+1h124 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct03:12+1h38Pakistan Railways
    Wed 7 Oct02:53+1h18Pakistan Railways
    Tue 6 Oct01:332m earlyPakistan Railways
    Mon 5 Oct02:41+1h06Pakistan Railways

    Seen on 4 of 5 days, ranging 2m early to +1h38. Every train at Rohri Jn. →

  • 5Bahawalpurscheduled 06:30+1h534 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct08:40+2h08Pakistan Railways
    Wed 7 Oct08:09+1h38Pakistan Railways
    Tue 6 Oct07:20+50mPakistan Railways
    Mon 5 Oct08:45+2h14Pakistan Railways

    Seen on 4 of 5 days, ranging +50m to +2h14. Every train at Bahawalpur →

  • 6Multan Canttscheduled 07:55+1h254 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct09:52+1h38Pakistan Railways
    Wed 7 Oct09:26+1h11Pakistan Railways
    Tue 6 Oct08:33+19mPakistan Railways
    Mon 5 Oct09:58+1h44Pakistan Railways

    Seen on 4 of 5 days, ranging +19m to +1h44. Every train at Multan Cantt →

  • 7Khanewal Jnscheduled 08:55+1h484 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct11:01+2h02Pakistan Railways
    Wed 7 Oct10:33+1h33Pakistan Railways
    Tue 6 Oct09:46+46mPakistan Railways
    Mon 5 Oct11:47+2h48Pakistan Railways

    Seen on 4 of 5 days, ranging +46m to +2h48. Every train at Khanewal Jn →

  • 8Sahiwalscheduled 10:23+1h474 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct12:26+2h02Pakistan Railways
    Wed 7 Oct11:57+1h32Pakistan Railways
    Tue 6 Oct11:46+1h22Pakistan Railways
    Mon 5 Oct13:36+3h11Pakistan Railways

    Seen on 4 of 5 days, ranging +1h22 to +3h11. Every train at Sahiwal →

  • 9Raiwind Jn.scheduled 11:50+1h574 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct14:08+2h14Pakistan Railways
    Wed 7 Oct13:34+1h39Pakistan Railways
    Tue 6 Oct13:27+1h32Pakistan Railways
    Mon 5 Oct15:13+3h18Pakistan Railways

    Seen on 4 of 5 days, ranging +1h32 to +3h18. Every train at Raiwind Jn. →

  • 10Kot Lakhpatscheduled 12:20+2h034 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct14:41+2h20Pakistan Railways
    Wed 7 Oct14:07+1h46Pakistan Railways
    Tue 6 Oct13:56+1h35Pakistan Railways
    Mon 5 Oct16:01+3h40Pakistan Railways

    Seen on 4 of 5 days, ranging +1h35 to +3h40. Every train at Kot Lakhpat →

  • 11Lahore Jn.scheduled 13:00+1h584 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct15:19+2h19Train GPS
    Wed 7 Oct14:36+1h36Train GPS
    Tue 6 Oct14:29+1h29Train GPS
    Mon 5 Oct17:00+4hTrain GPS

    Seen on 4 of 5 days, ranging +1h29 to +4h. Every train at Lahore Jn. →

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 15UP
Karachiexp · CC BY-SA 3.0

Common questions

Is Karachi Express 15UP usually late?

Typically 188 minutes late arriving at Lahore Jn., measured across 30 recorded arrivals (30 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 15UP on a bad day?

On the worst one run in ten, 291 minutes late into Lahore Jn., against a typical 188 minutes late. Both come from the same 30 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 15UP leave Karachi Cantt?

18:00, on the current published timetable. It is booked into Lahore Jn. at 13:00, 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 15UP take from Karachi Cantt to Lahore Jn.?

19h on the timetable. In practice a typical run has taken 22h 08m, measured from recorded arrivals at Lahore Jn..

How many stops does Karachi Express 15UP make?

11 on the current published timetable, from Karachi Cantt to Lahore Jn.. 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 15UP 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 Karachi–Lahore 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.