RE24 4736 Luzern – Olten

View line RE24

Luzern 20:05 → Olten 20:52 Daily 0 h 47 min · 11 stops SBB CFF FFS

Running now · updated 20:36

Position estimated from the timetable

Between Nebikon and Dagmersellen 0 min

Estimated arrival at Olten 20:52 · 67 km/h

  1. Luzern20:05
  2. Rothenburg Station20:16
  3. Sempach-Neuenkirch20:20
  4. Wauwil20:31
  5. Nebikon20:35
  6. Dagmersellen20:38
  7. Olten20:52

Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 30 runs arrived on time.

On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
94%
47/50 runs under 3 min
RT coverage: 49 full · 1 partial · 0 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: +3 min

Last 30 days

Arrival delay at Olten, 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 +6 min · last fix heading to Olten +6 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Olten +5 min
  • Sat 7 Nov Max en route +6 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 47
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 50 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
20:05on time on timePassed
20:10 / 20:11≈ on time ≈ on timePassed
20:16≈ on time ≈ +1 minPassed
20:20≈ on time ≈ +1 minPassed
20:26 / 20:27≈ on time ≈ +1 minPassed
20:31≈ on time ≈ +1 minPassed
20:35≈ on time ≈ +1 minPassed
20:38≈ on time ≈ +2 minNext
20:40≈ on time ≈ +2 min
20:44 / 20:45≈ on time ≈ +2 min
20:52on 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
Thu 19 NovNebikon 20:34Partial coverage0 min—
Wed 18 NovOlten 20:54+3 min+3 min
Tue 17 NovOlten 20:54+1 min—
Mon 16 NovOlten 20:57+5 min+5 min
Sun 15 NovOlten 20:530 min—
Sat 14 NovOlten 20:520 min—
Fri 13 NovOlten 20:540 min—
Thu 12 NovOlten 20:54+1 min—
Wed 11 NovOlten 20:54+1 min+1 min
Tue 10 NovOlten 20:530 min—
Mon 9 NovOlten 20:530 min—
Sun 8 NovOlten 20:54+1 min+1 min
Sat 7 NovOlten 20:54+3 min+6 min
Fri 6 NovOlten 20:59+6 min+6 min
Thu 5 NovOlten 20:530 min—
Wed 4 NovOlten 20:53−1 min—
Tue 3 NovOlten 20:54+1 min—
Mon 2 NovOlten 20:54+2 min+2 min
Sun 1 NovOlten 20:530 min—
Sat 31 OctOlten 20:530 min—
Fri 30 OctOlten 20:530 min—
Thu 29 OctOlten 20:530 min—
Wed 28 OctOlten 20:55+2 min+2 min
Tue 27 OctOlten 20:54+1 min—
Mon 26 OctOlten 20:530 min—
Sun 25 OctOlten 20:520 min—
Sat 24 OctOlten 20:54+1 min+1 min
Fri 23 OctOlten 20:530 min—
Thu 22 OctOlten 20:54+1 min—
Wed 21 OctOlten 20:520 min—