IR27 2471 Basel SBB – Luzern

View line IR27

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

Running now · updated 12:58

Position estimated from the timetable

Between Zofingen and Sursee No data

Estimated arrival at Luzern 13:30 · 79 km/h

  1. Basel SBB12:16
  2. Liestal12:25
  3. Sissach12:33
  4. Olten12:49
  5. Zofingen12:57
  6. Sursee13:11
  7. Luzern13:30
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Wed 11 Nov Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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