IR27 2461 Basel SBB – Luzern

View line IR27

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

Running now · updated 07:47

Position estimated from the timetable

Between Gelterkinden and Olten 0 min

Estimated arrival at Luzern 08:30 · 78 km/h

  1. Basel SBB07:16
  2. Liestal07:25
  3. Sissach07:33
  4. Gelterkinden07:37
  5. Olten07:49
  6. Zofingen07:57
  7. Luzern08:30

Today it is running no worse than usual: typical arrival delay is +1 min; 82% of the last 28 runs arrived on time.

On-time · 30 days
82%
23/28 runs under 3 min
RT coverage: 27 full · 1 partial · 2 no data
On-time · 90 days
80%
37/46 runs under 3 min
RT coverage: 45 full · 1 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 17 Nov Max en route +6 min · last fix heading to Luzern +6 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Tue 13 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Luzern +5 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 37
  • 3–10 min 20% · 9
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
07:16on time on timePassed
07:25 / 07:26≈ on time ≈ +1 minPassed
07:33≈ on time ≈ +1 minPassed
07:37≈ on time ≈ +1 minPassed
07:49 / 07:50≈ on time ≈ +2 minNext
07:57 / 07:58≈ +1 min ≈ +2 min
08:11 / 08:12≈ +1 min ≈ +3 min
08:30+1 min +4 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
Thu 19 NovOlten 07:44Partial coverage0 min—
Wed 18 NovLuzern 08:33+2 min+2 min
Tue 17 NovLuzern 08:37+6 min+6 min
Mon 16 NovLuzern 08:34+3 min+3 min
Sun 15 NovLuzern 08:290 min—
Sat 14 NovLuzern 08:32+1 min—
Fri 13 NovLuzern 08:34+4 min+4 min
Thu 12 NovLuzern 08:32No data—
Wed 11 NovLuzern 08:32+1 min+1 min
Tue 10 NovLuzern 08:34+4 min+4 min
Mon 9 NovLuzern 08:29+1 min—
Sun 8 NovLuzern 08:29−1 min—
Sat 7 NovLuzern 08:290 min—
Fri 6 NovLuzern 08:33+2 min+2 min
Thu 5 NovLuzern 08:32+1 min+1 min
Wed 4 NovLuzern 08:32+1 min+1 min
Tue 3 NovLuzern 08:34+3 min+3 min
Mon 2 NovLuzern 08:32+1 min—
Sun 1 NovLuzern 08:310 min—
Sat 31 OctLuzern 08:310 min—
Fri 30 OctLuzern 08:310 min—
Thu 29 OctLuzern 08:32+1 min+1 min
Wed 28 OctLuzern 08:35+3 min+3 min
Tue 27 OctLuzern 08:320 min—
Mon 26 OctLuzern 08:32No data—
Sun 25 OctLuzern 08:310 min—
Sat 24 OctLuzern 08:35+4 min+4 min
Fri 23 OctLuzern 08:33+2 min+2 min
Thu 22 OctLuzern 08:320 min—
Wed 21 OctLuzern 08:34+3 min+3 min