RE24 4723 Olten – Luzern

View line RE24

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:06 from Olten · Thu 5 Nov

Next departure 13:06 today · Olten
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 23% · 7
  • On time 77% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=6
  • 100% T n=2
  • 100% F n=6
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

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