latetrains.pkLate, on record44 live
Trains/Karachi–Lahore/Pak Business 33UP

33 Pak Business 33UP پاک بزنس 33 اپ

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

Running 39 min late — heading for Nawabshah Jn., due 20:52 (operator's estimate), 76 km/h. Last crossed Hyderabad 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 Lahore Jn.+3h 24mmedian of 40 recorded arrivals · 31 Jul – 8 Oct 2026
Typical delay, any stop+2h 01mat 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 28mworse than nine tenths of recorded stop arrivals

9 days of recorded arrivals.

Over 40 recorded arrivals (31 Jul – 8 Oct 2026), Pak Business 33UP has typically reached Lahore Jn. around 13:44 the day after it leaves — on the worst one run in ten, past 17:44 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 18h 20m — Karachi Cantt to Lahore Jn.. Typically 21h 44m, 3h 24m longer.

Timetable: out 16:00, in at 10:20 the next day — one night on board.

What these figures cover
  • Scheduled — the current timetable, Karachi Cantt 16:00 to Lahore Jn. 10:20 the next day
  • Typical journey — from the scheduled departure to the recorded arrival at Lahore Jn.; the median of 40 runs
  • Bad day — 25h 44m 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 15m · 4 runs
Tue+1h 57m · 4 runs
Wed+2h 53m · 5 runs
Thu+4h 37m · 5 runs
Fri+3h 09m · 5 runs
Sat+3h 19m · 4 runs
Sun+4h 09m · 5 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 +23 min · reaches Lahore Jn. +3h 24m — +3h 01m lost along the way.

  1. Karachi Cantt16:00کراچی کينٹ+23 min
  2. Hyderabad Jn18:40حیدرآباد جنکشن+1h 41m
  3. Nawabshah Jn.20:15نوابشاہ جنکشن+2h 21m
  4. Rohri Jn.23:35روہڑی جنکشن+2h 11m
  5. Rahim Yar Khan02:24رحیم یار خان+2h 35m
  6. Bahawalpur04:45بہاولپور+2h 56m
  7. Khanewal Jn06:25خانیوال+2h 59m
  8. Sahiwal07:54ساہِيوال+3h 11m
  9. Raiwind Jn.09:19راۓوِنڈ جنکشن+3h 21m
  10. Kot Lakhpat09:47کوٹ لکھپت+3h 05m
  11. Lahore Jn.10:20لاہور جنکشن+3h 24m

Where it stands longest past the timetableshortest to longest recorded

  1. Rohri Jn.scheduled 25 min24 min–1h 09m
  2. Khanewal Jnscheduled 20 min20 min–1h 44m
  3. Hyderabad Jnscheduled 5 min8–40 min
  4. Sahiwalscheduled 2 min3–14 min
  5. Rahim Yar Khanscheduled 2 min2–12 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 18m)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 9 October 2026 run

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

#StationArrivalDeparture
1Karachi Cantt—16:00
2Hyderabad Jn18:35 → 19:14·PR18:40 → 19:15
3Nawabshah Jn.20:1320:15
⋯ 6 stops
4Rohri Jn.23:1023:35
5Rahim Yar Khan02:22 +1d02:24 +1d
6Bahawalpur04:43 +1d04:45 +1d
7Khanewal Jn06:05 +1d06:25 +1d
8Sahiwal07:52 +1d07:54 +1d
9Raiwind Jn.09:15 +1d09:19 +1d
10Kot Lakhpat09:45 +1d09:47 +1d
11Lahore Jn.10:20 +1d—
What the marks mean
  • → 21:28 — actual time on the 9 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: 23 August 2026 →

Station by station, last 5 days

40 arrivals recorded

One mark per day, newest first.

Days shownFri9 OctThu8 OctWed7 OctMon5 OctSun4 Oct

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

  • 2Hyderabad Jnscheduled 18:35+58m5 days
    DayArrivedDelayRecorded by
    Fri 9 Oct19:14+35mPakistan Railways
    Thu 8 Oct19:37+58mPakistan Railways
    Wed 7 Oct20:20+1h45Pakistan Railways
    Mon 5 Oct18:46+6mPakistan Railways
    Sun 4 Oct21:37+2h58Pakistan Railways

    Seen on 5 of 5 days, ranging +6m to +2h58. Every train at Hyderabad Jn →

  • 3Nawabshah Jn.scheduled 20:13+1h534 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct21:46+1h32Pakistan Railways
    Wed 7 Oct22:28+2h13Pakistan Railways
    Mon 5 Oct20:32+18mPakistan Railways
    Sun 4 Oct23:34+3h19Pakistan Railways

    Seen on 4 of 5 days, ranging +18m to +3h19. Every train at Nawabshah Jn. →

  • 4Rohri Jn.scheduled 23:10+2h324 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct02:29+2h53Pakistan Railways
    Wed 7 Oct01:20+2h10Pakistan Railways
    Mon 5 Oct22:5936m earlyPakistan Railways
    Sun 4 Oct02:20+3h10Pakistan Railways

    Seen on 4 of 5 days, ranging 36m early to +3h10. Every train at Rohri Jn. →

  • 5Rahim Yar Khanscheduled 02:22+2h434 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct05:19+2h56Pakistan Railways
    Wed 7 Oct04:53+2h30Pakistan Railways
    Mon 5 Oct02:32+8mPakistan Railways
    Sun 4 Oct05:43+3h19Pakistan Railways

    Seen on 4 of 5 days, ranging +8m to +3h19. Every train at Rahim Yar Khan →

  • 6Bahawalpurscheduled 04:43+2h454 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct07:38+2h53Pakistan Railways
    Wed 7 Oct07:20+2h37Pakistan Railways
    Mon 5 Oct05:25+40mPakistan Railways
    Sun 4 Oct08:20+3h37Pakistan Railways

    Seen on 4 of 5 days, ranging +40m to +3h37. Every train at Bahawalpur →

  • 7Khanewal Jnscheduled 06:05+2h384 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct09:13+2h44Pakistan Railways
    Wed 7 Oct08:56+2h32Pakistan Railways
    Mon 5 Oct06:45+21mPakistan Railways
    Sun 4 Oct10:34+4h09Pakistan Railways

    Seen on 4 of 5 days, ranging +21m to +4h09. Every train at Khanewal Jn →

  • 8Sahiwalscheduled 07:52+3h054 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct11:11+3h18Pakistan Railways
    Wed 7 Oct10:46+2h52Pakistan Railways
    Mon 5 Oct08:51+58mPakistan Railways
    Sun 4 Oct12:20+4h28Pakistan Railways

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

  • 9Raiwind Jn.scheduled 09:15+3h194 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct12:50+3h32Pakistan Railways
    Wed 7 Oct12:20+3h05Pakistan Railways
    Mon 5 Oct10:30+1h11Pakistan Railways
    Sun 4 Oct14:16+4h58Pakistan Railways

    Seen on 4 of 5 days, ranging +1h11 to +4h58. Every train at Raiwind Jn. →

  • 10Kot Lakhpatscheduled 09:45+3h204 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct13:19+3h34Pakistan Railways
    Wed 7 Oct12:51+3h05Pakistan Railways
    Mon 5 Oct11:02+1h15Pakistan Railways
    Sun 4 Oct14:49+5h02Pakistan Railways

    Seen on 4 of 5 days, ranging +1h15 to +5h02. Every train at Kot Lakhpat →

  • 11Lahore Jn.scheduled 10:20+3h033 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Thu 8 Oct13:56+3h36Train GPS
    Wed 7 Oct13:22+3h03Train GPS
    Mon 5 Oct11:33+1h13Train GPS
    Sun 4 Octnot recorded—

    Seen on 3 of 5 days, ranging +1h13 to +3h36. 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.

Common questions

Is Pak Business 33UP usually late?

Typically 204 minutes late arriving at Lahore Jn., measured across 40 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 Pak Business 33UP on a bad day?

On the worst one run in ten, 444 minutes late into Lahore Jn., against a typical 204 minutes late. Both come from the same 40 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 Pak Business 33UP leave Karachi Cantt?

16:00, on the current published timetable. It is booked into Lahore Jn. at 10:20, the day after it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does Pak Business 33UP take from Karachi Cantt to Lahore Jn.?

18h 20m on the timetable. In practice a typical run has taken 21h 44m, measured from recorded arrivals at Lahore Jn..

How many stops does Pak Business 33UP 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 Pak Business 33UP 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.