latetrains.pkLate, on record44 live
Trains/Lahore–Pakpattan/Bhullhe Shah passengers 258Dn

258 Bhullhe Shah passengers 258Dn بھلے شاہ پسنجرز 258 ڈاؤن

Kitni late hoti hai? Typical delay, on-time record aur station timings.
LAHOREPAKPATTANLAHORE
Down direction · returnsلاہور جنکشن ۔ پاکپتن ۔ لاہور جنکشن
PassengerLast seen 8 September 202671 days tracked

How late is it, usually?

no figure yet
Since 31 July 2026

One day recorded so far.

A typical (median) delay figure appears at 7 full days of recorded runs — days the train reported, not calendar days.

Recorded days
1 / 7
Positions logged
53,328
Stops timed
11

1 of 7 recorded days toward a first typical-delay figure

Where the time goes

most of it lost after Kot Lakhpat

Leaves Kot Lakhpat +31 min · reaches Pakpattan +2h 37m — +2h 06m lost along the way.

  1. Lahore Jn.16:00لاہور جنکشن—
  2. Kot Lakhpat16:30کوٹ لکھپت+31 min
  3. Raiwind Jn.17:02راۓوِنڈ جنکشن+45 min
  4. Kasur Jn18:05قصور جنکشن+48 min
  5. Khudian18:36کھڈیاں+1h 42m
  6. Usmanwala18:52عثمان والا+1h 48m
  7. Kanganpur19:31کنگن پور+1h 58m
  8. Mandi Ahmadabad20:00منڈی احمد آباد+1h 57m
  9. Basirpur20:26بصيرپور+2h 10m
  10. Haveli Wasawewala20:52حویلی واساویلا+2h 17m
  11. Pakpattan21:30پاکپتن+2h 37m

Where it stands longest past the timetableshortest to longest recorded

  1. Kasur Jnscheduled 30 min36 min–1h 55m
  2. Kot Lakhpatscheduled 2 min1 min–1h 40m
  3. Usmanwalascheduled 2 min1–43 min
  4. Basirpurscheduled 2 min3–45 min
  5. Mandi Ahmadabadscheduled 2 min2–56 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 Kasur Jn and Khudian (+54 min)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 7 September 2026 run

The second time in a cell is what actually happened on the 7 September 2026 run. See the whole run →

#StationArrivalDeparture
1Lahore Jn.—16:00
2Kot Lakhpat16:28 → 17:3916:30 → 17:40
3Raiwind Jn.16:57 → 18:1617:02 → 18:20
4Kasur Jn17:35 → 19:0918:05 → 20:02
5Khudian18:34 → 20:4118:36 → 20:43
6Usmanwala18:50 → 21:0518:52 → 21:09
7Kanganpur19:29 → 21:3919:31 → 21:41
8Mandi Ahmadabad19:58 → 22:0520:00 → 22:09
9Basirpur20:24 → 22:3920:26 → 23:02
10Haveli Wasawewala20:50 → 23:2820:52 → 23:32
11Pakpattan21:30 → 00:3121:30 → 00:33
What the marks mean
  • → 21:28 — actual time on the 7 September 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

46 arrivals recorded

One mark per day, newest first.

Days shownMon7 SeptSun6 SeptSat5 SeptFri4 SeptThu3 Sept

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

  • 2Kot Lakhpatscheduled 16:28+28m5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept17:39+1h11Pakistan Railways (journey record)
    Sun 6 Sept17:33+1h05Pakistan Railways (journey record)
    Sat 5 Sept16:39+12mPakistan Railways (journey record)
    Fri 4 Sept16:55+28mPakistan Railways (journey record)
    Thu 3 Sept16:29+2mPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +2m to +1h11. Every train at Kot Lakhpat →

  • 3Raiwind Jn.scheduled 16:57+57m4 days
    DayArrivedDelayRecorded by
    Mon 7 Sept18:16+1h19Pakistan Railways (journey record)
    Sun 6 Sept18:22+1h26Pakistan Railways (journey record)
    Sat 5 Septnot recorded—
    Fri 4 Sept17:31+34mPakistan Railways (journey record)
    Thu 3 Sept17:10+13mPakistan Railways (journey record)

    Seen on 4 of 5 days, ranging +13m to +1h26. Every train at Raiwind Jn. →

  • 4Kasur Jnscheduled 17:35+43m5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept19:09+1h35Pakistan Railways (journey record)
    Sun 6 Sept19:11+1h37Pakistan Railways (journey record)
    Sat 5 Sept17:59+24mPakistan Railways (journey record)
    Fri 4 Sept18:18+43mPakistan Railways (journey record)
    Thu 3 Sept17:52+17mPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +17m to +1h37. Every train at Kasur Jn →

  • 5Khudianscheduled 18:34+1h394 days
    DayArrivedDelayRecorded by
    Mon 7 Sept20:41+2h08Pakistan Railways (journey record)
    Sun 6 Sept21:05+2h31Pakistan Railways (journey record)
    Sat 5 Sept19:43+1h10Pakistan Railways (journey record)
    Fri 4 Septnot recorded—
    Thu 3 Sept19:40+1h07Pakistan Railways (journey record)

    Seen on 4 of 5 days, ranging +1h07 to +2h31. Every train at Khudian →

  • 6Usmanwalascheduled 18:50+1h395 days
    DayArrivedDelayRecorded by
    Mon 7 Sept21:05+2h15Pakistan Railways (journey record)
    Sun 6 Sept21:29+2h40Pakistan Railways (journey record)
    Sat 5 Sept20:03+1h14Pakistan Railways (journey record)
    Fri 4 Sept20:29+1h39Pakistan Railways (journey record)
    Thu 3 Sept20:02+1h12Pakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +1h12 to +2h40. Every train at Usmanwala →

  • 7Kanganpurscheduled 19:29+2h035 days
    DayArrivedDelayRecorded by
    Mon 7 Sept21:39+2h11Pakistan Railways (journey record)
    Sun 6 Sept22:13+2h44Pakistan Railways (journey record)
    Sat 5 Sept20:53+1h25Pakistan Railways (journey record)
    Fri 4 Sept21:32+2h03Pakistan Railways (journey record)
    Thu 3 Sept21:11+1h43Pakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +1h25 to +2h44. Every train at Kanganpur →

  • 8Mandi Ahmadabadscheduled 19:58+2h045 days
    DayArrivedDelayRecorded by
    Mon 7 Sept22:05+2h07Pakistan Railways (journey record)
    Sun 6 Sept22:44+2h46Pakistan Railways (journey record)
    Sat 5 Sept21:19+1h22Pakistan Railways (journey record)
    Fri 4 Sept22:02+2h04Pakistan Railways (journey record)
    Thu 3 Sept21:36+1h38Pakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +1h22 to +2h46. Every train at Mandi Ahmadabad →

  • 9Basirpurscheduled 20:24+2h145 days
    DayArrivedDelayRecorded by
    Mon 7 Sept22:39+2h15Pakistan Railways (journey record)
    Sun 6 Sept23:29+3h05Pakistan Railways (journey record)
    Sat 5 Sept21:55+1h32Pakistan Railways (journey record)
    Fri 4 Sept22:38+2h14Pakistan Railways (journey record)
    Thu 3 Sept22:08+1h45Pakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +1h32 to +3h05. Every train at Basirpur →

  • 10Haveli Wasawewalascheduled 20:50+2h235 days
    DayArrivedDelayRecorded by
    Mon 7 Sept23:28+2h38Pakistan Railways (journey record)
    Sun 6 Sept00:03+3h13Pakistan Railways (journey record)
    Sat 5 Sept22:27+1h37Pakistan Railways (journey record)
    Fri 4 Sept23:13+2h23Pakistan Railways (journey record)
    Thu 3 Sept22:38+1h48Pakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +1h37 to +3h13. Every train at Haveli Wasawewala →

  • 11Pakpattanscheduled 21:30+3h013 days
    DayArrivedDelayRecorded by
    Mon 7 Sept00:31+3h01Pakistan Railways (journey record)
    Sun 6 Sept01:20+3h51Pakistan Railways (journey record)
    Sat 5 Septnot recorded—
    Fri 4 Septnot recorded—
    Thu 3 Sept23:34+2h05Pakistan Railways (journey record)

    Seen on 3 of 5 days, ranging +2h05 to +3h51. Every train at Pakpattan →

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 Bhullhe Shah passengers 258Dn usually late?

Typically 157 minutes late arriving at Pakpattan, measured across 22 recorded arrivals (1 Aug – 7 Sep 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 Bhullhe Shah passengers 258Dn on a bad day?

On the worst one run in ten, 209 minutes late into Pakpattan, against a typical 157 minutes late. Both come from the same 22 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 Bhullhe Shah passengers 258Dn leave Lahore Jn.?

16:00, on the current published timetable. It is booked into Pakpattan at 21:30, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does Bhullhe Shah passengers 258Dn take from Lahore Jn. to Pakpattan?

5h 30m on the timetable. In practice a typical run has taken 8h 07m, measured from recorded arrivals at Pakpattan.

How many stops does Bhullhe Shah passengers 258Dn make?

11 on the current published timetable, from Lahore Jn. to Pakpattan. 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.

All Lahore–Pakpattan trains →
Fareed Express 38DN38
فرید ایکسپریس 38 ڈائون
Lahore Jn. To Karachi City