RE24 4718 Luzern – Olten
Alerts for train 4718
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line RE24.
It has not run yet today
Last recorded run: Friday 13 November 0 min
Next service: today 11:05 from Luzern · Sat 14 Nov
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
- Mon 5 Oct Max en route +11 min · last fix heading to Olten +11 min
- Sun 25 Oct Max en route +4 min · last fix heading to Olten +4 min
Distribution · 90 days
31 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 29
- 3–10 min 3% · 1
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- 100% T n=5
- 100% W n=6
- 100% T n=1
- 100% F n=6
- 100% S n=5
- 86% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 31 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 11:05 | on time | on time | |
| 11:10 / 11:11 | ≈ on time | ≈ on time | |
| 11:16 | ≈ on time | ≈ +1 min | |
| 11:20 | ≈ on time | ≈ +1 min | |
| 11:26 / 11:27 | ≈ on time | ≈ +1 min | |
| 11:31 | ≈ on time | ≈ +1 min | |
| 11:35 | ≈ on time | ≈ +1 min | |
| 11:38 | ≈ on time | ≈ +1 min | |
| 11:40 | ≈ on time | ≈ +1 min | |
| 11:44 / 11:45 | ≈ on time | ≈ +2 min | |
| 11:52 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 13 Nov | Olten 11:53 | 0 min | — |
| Thu 12 Nov | Olten 11:53 | No data | — |
| Wed 11 Nov | Olten 11:53 | 0 min | — |
| Tue 10 Nov | Olten 11:54 | +1 min | +1 min |
| Mon 9 Nov | Olten 11:53 | No data | — |
| Sun 8 Nov | Olten 11:54 | +2 min | +2 min |
| Sat 7 Nov | Olten 11:53 | 0 min | — |
| Fri 6 Nov | Olten 11:53 | 0 min | — |
| Thu 5 Nov | Olten 11:53 | No data | — |
| Wed 4 Nov | Olten 11:53 | 0 min | — |
| Tue 3 Nov | Olten 11:54 | 0 min | — |
| Mon 2 Nov | Olten 11:53 | No data | — |
| Sun 1 Nov | Olten 11:53 | 0 min | — |
| Sat 31 Oct | Olten 11:53 | 0 min | — |
| Fri 30 Oct | Olten 11:53 | 0 min | — |
| Thu 29 Oct | Olten 11:53 | No data | — |
| Wed 28 Oct | Olten 11:54 | +1 min | +1 min |
| Tue 27 Oct | Olten 11:53 | 0 min | — |
| Mon 26 Oct | Olten 11:54 | No data | — |
| Sun 25 Oct | Olten 11:57 | +4 min | +4 min |
| Sat 24 Oct | Olten 11:53 | 0 min | — |
| Fri 23 Oct | Olten 11:53 | 0 min | — |
| Thu 22 Oct | Olten 11:53 | No data | — |
| Wed 21 Oct | Olten 11:54 | +1 min | — |
| Tue 20 Oct | Olten 11:55 | +2 min | +2 min |
| Mon 19 Oct | Olten 11:53 | No data | — |
| Sun 18 Oct | Olten 11:56 | +2 min | +2 min |
| Sat 17 Oct | Olten 11:53 | 0 min | — |
| Fri 16 Oct | Olten 11:52 | 0 min | — |
| Thu 15 Oct | Olten 11:53 | No data | — |