RE24 4738 Luzern → Olten

View line RE24

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

RE24 4738 Luzern–Olten: final delay under 3 min on 23 of its 26 runs with data in the last 30 days (88%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:08 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: tomorrow 21:05 from Luzern · Mon 23 Nov

Next departure 21:05 tomorrow · Luzern
On-time · 30 days
88%
23/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
89%
41/46 runs under 3 min
RT coverage: 46 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Sat 3 Oct Max en route +14 min · last fix heading to Dagmersellen +14 min
  • Sun 4 Oct Max en route +12 min · last fix heading to Olten +12 min
  • Mon 16 Nov Max en route +8 min · last fix heading to Olten +8 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Tue 3 Nov Max en route +4 min · last fix heading to Olten +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 89% · 41
  • 3–10 min 7% · 3
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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 10
21:05on time on time
21:10 / 21:11≈ on time ≈ +1 min
21:16≈ on time ≈ +1 min
21:20≈ on time ≈ +1 min
21:26 / 21:27≈ on time ≈ +1 min
21:31≈ on time ≈ +2 min
21:35≈ on time ≈ +2 min
21:38≈ on time ≈ +2 min
21:40≈ on time ≈ +2 min
21:44 / 21:45≈ on time ≈ +2 min
21:52on time +3 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
Sat 21 NovOlten 21:530 min—
Fri 20 NovOlten 21:520 min—
Thu 19 NovOlten 21:530 min—
Wed 18 NovOlten 21:520 min—
Tue 17 NovOlten 21:57+4 min+4 min
Mon 16 NovOlten 21:59+8 min+8 min
Sun 15 NovOlten 21:53No data—
Sat 14 NovOlten 21:520 min—
Fri 13 NovOlten 21:530 min—
Thu 12 NovOlten 21:55+2 min+2 min
Wed 11 NovOlten 21:530 min—
Tue 10 NovOlten 21:530 min—
Mon 9 NovOlten 21:540 min—
Sun 8 NovOlten 21:530 min—
Sat 7 NovOlten 21:530 min—
Fri 6 NovOlten 21:540 min—
Thu 5 NovOlten 21:530 min—
Wed 4 NovOlten 21:53No data—
Tue 3 NovOlten 21:57+4 min+4 min
Mon 2 NovOlten 21:530 min—
Sun 1 NovOlten 21:530 min—
Sat 31 OctOlten 21:530 min—
Fri 30 OctOlten 21:52−1 min—
Thu 29 OctOlten 21:530 min—
Wed 28 OctOlten 21:53No data—
Tue 27 OctOlten 21:530 min—
Mon 26 OctOlten 21:530 min—
Sun 25 OctOlten 21:54+1 min—
Sat 24 OctOlten 21:530 min—
Fri 23 OctOlten 21:54+1 min+1 min