RE24 4715 Olten – Luzern

View line RE24

Olten 09:06 → Luzern 09:55 Daily 0 h 49 min · 11 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Luzern at 09:59 +4 min

  1. Olten09:06
  2. Reiden09:16
  3. Dagmersellen09:19
  4. Wauwil09:26
  5. Sempach-Neuenkirch09:37
  6. Rothenburg Station09:42
  7. Luzern09:55

Next service: tomorrow 09:06 from Olten · Thu 12 Nov

Next departure 09:06 tomorrow · Olten
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 2 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

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

Distribution · 90 days

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

  • Early 43% · 17
  • On time 53% · 21
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 40 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 10
09:06on time on time
09:12 / 09:13≈ on time ≈ on time
09:16≈ on time ≈ on time
09:19≈ on time ≈ +1 min
09:22≈ on time ≈ +1 min
09:26≈ on time ≈ +1 min
09:30 / 09:31≈ on time ≈ +1 min
09:37≈ 1 min early ≈ +1 min
09:42≈ 1 min early ≈ +1 min
09:47≈ 1 min early ≈ +1 min
09:551 min early +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
Wed 11 NovLuzern 09:59+4 min+4 min
Tue 10 NovLuzern 09:54−1 min—
Mon 9 NovLuzern 09:540 min—
Sun 8 NovLuzern 09:570 min—
Sat 7 NovLuzern 09:54−1 min—
Fri 6 NovLuzern 09:54−1 min—
Thu 5 NovLuzern 09:54−2 min—
Wed 4 NovLuzern 09:54−2 min—
Tue 3 NovLuzern 09:540 min—
Mon 2 NovLuzern 09:54−2 min—
Sun 1 NovLuzern 09:55−1 min—
Sat 31 OctLuzern 09:58+2 min+2 min
Fri 30 OctLuzern 09:54−2 min—
Thu 29 OctLuzern 09:56No data—
Wed 28 OctLuzern 09:570 min—
Tue 27 OctLuzern 09:54−2 min—
Mon 26 OctOlten 11:010 min—
Sun 25 OctLuzern 09:56No data—
Sat 24 OctLuzern 10:02+6 min+6 min
Fri 23 OctLuzern 09:550 min—
Thu 22 OctLuzern 09:57+1 min+1 min
Wed 21 OctLuzern 09:54−2 min—
Tue 20 OctLuzern 09:57+1 min—
Mon 19 OctLuzern 09:54−2 min—
Sun 18 OctLuzern 09:55−1 min—
Sat 17 OctLuzern 09:58+2 min+2 min
Fri 16 OctLuzern 09:54−2 min—
Thu 15 OctLuzern 09:58+2 min+2 min
Wed 14 OctLuzern 09:560 min—
Tue 13 OctLuzern 09:55−1 min—