IR27 2465 Basel SBB – Luzern

View line IR27

Basel SBB 09:16 → Luzern 10:30 Daily 1 h 14 min · 8 stops SBB CFF FFS

Running now · updated 10:05

Position estimated from the timetable

Between Zofingen and Sursee No data

Estimated arrival at Luzern 10:30 · 82 km/h

  1. Basel SBB09:16
  2. Liestal09:25
  3. Sissach09:33
  4. Olten09:49
  5. Zofingen09:57
  6. Sursee10:11
  7. Luzern10:30
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
95%
41/43 runs under 3 min
RT coverage: 43 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Luzern, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 6 Nov Max en route +16 min · last fix heading to Strasbourg +16 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Luzern +3 min

Distribution · 90 days

43 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 95% · 41
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • 100% S n=6
  • 86% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 43 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10Today
09:16on time on timePassed
09:25 / 09:26≈ on time ≈ on timePassed
09:33≈ on time ≈ +1 minPassed
09:37≈ on time ≈ +1 minPassed
09:49 / 09:50≈ on time ≈ +1 minPassed
09:57 / 09:58≈ on time ≈ +1 minPassed
10:11 / 10:12≈ +1 min ≈ +2 minNext
10:30+1 min +2 min

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Mon 16 NovSursee 10:05Partial coverageNo data—
Sun 15 NovStrasbourg 22:12+2 min+2 min
Sat 14 NovStrasbourg 22:13+2 min+2 min
Fri 13 NovStrasbourg 22:240 min—
Thu 12 NovStrasbourg 22:25+2 min+2 min
Wed 11 NovStrasbourg 22:24+1 min+2 min
Tue 10 NovStrasbourg 22:240 min—
Mon 9 NovStrasbourg 22:24+2 min+2 min
Sun 8 NovStrasbourg 22:12+2 min+2 min
Sat 7 NovStrasbourg 22:120 min—
Fri 6 NovStrasbourg 22:27+16 min+16 min
Thu 5 NovStrasbourg 22:230 min—
Wed 4 NovStrasbourg 22:240 min—
Tue 3 NovStrasbourg 22:240 min—
Mon 2 NovStrasbourg 22:24+2 min+2 min
Sun 1 NovStrasbourg 22:12+1 min—
Sat 31 OctLuzern 10:32+1 min—
Fri 30 OctLuzern 10:310 min—
Thu 29 OctLuzern 10:320 min—
Wed 28 OctLuzern 10:33+1 min+1 min
Tue 27 OctLuzern 10:310 min—
Mon 26 OctLuzern 10:320 min+1 min
Sun 25 OctLuzern 10:34+3 min+3 min
Sat 24 OctLuzern 10:32+1 min—
Fri 23 OctLuzern 10:33+2 min+2 min
Thu 22 OctLuzern 10:32+1 min—
Wed 21 OctLuzern 10:32+1 min+1 min
Tue 20 OctLuzern 10:33+2 min+2 min
Mon 19 OctLuzern 10:32+1 min—
Sun 18 OctLuzern 10:320 min—