RE24 4726 Luzern – Olten
Alerts for train 4726
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.
Running now · updated 15:38
Position estimated from the timetable
Between Dagmersellen and Reiden 0 min
Estimated arrival at Olten 15:52 · 36 km/h
- Luzern15:05
- Rothenburg Station15:16
- Sempach-Neuenkirch15:20
- Wauwil15:31
- Dagmersellen15:38
- Reiden15:40
- Olten15:52
Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 29 runs arrived on time.
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 24 Oct Max en route +20 min · last fix heading to Zofingen +20 min
- Sun 25 Oct Max en route +7 min · last fix heading to Olten +7 min
- Fri 6 Nov Max en route +5 min · last fix heading to Olten +5 min
Distribution · 90 days
42 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 39
- 3–10 min 5% · 2
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=5
- 100% W n=6
- 100% T n=6
- 83% F n=6
- 86% S n=7
- 83% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 42 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 | Today |
|---|---|---|---|---|
| 15:05 | on time | on time | Passed | |
| 15:10 / 15:11 | ≈ on time | ≈ on time | Passed | |
| 15:16 | ≈ on time | ≈ +1 min | Passed | |
| 15:20 | ≈ on time | ≈ +1 min | Passed | |
| 15:26 / 15:27 | ≈ on time | ≈ +1 min | Passed | |
| 15:31 | ≈ on time | ≈ +1 min | Passed | |
| 15:35 | ≈ on time | ≈ +1 min | Passed | |
| 15:38 | ≈ on time | ≈ +1 min | Passed | |
| 15:40 | ≈ on time | ≈ +2 min | ||
| 15:44 / 15:45 | ≈ on time | ≈ +2 min | ||
| 15: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 |
|---|---|---|---|
| Sat 14 Nov | Nebikon 15:34Partial coverage | 0 min | — |
| Fri 13 Nov | Olten 15:54 | +1 min | +1 min |
| Thu 12 Nov | Olten 15:53 | 0 min | — |
| Wed 11 Nov | Olten 15:53 | 0 min | — |
| Tue 10 Nov | Olten 15:54 | +1 min | +1 min |
| Mon 9 Nov | Olten 15:53 | +1 min | — |
| Sun 8 Nov | Olten 15:53 | 0 min | — |
| Sat 7 Nov | Olten 15:53 | 0 min | — |
| Fri 6 Nov | Olten 15:57 | +5 min | +5 min |
| Thu 5 Nov | Olten 15:54 | +2 min | +2 min |
| Wed 4 Nov | Olten 15:53 | 0 min | — |
| Tue 3 Nov | Olten 15:53 | No data | — |
| Mon 2 Nov | Olten 15:54 | 0 min | — |
| Sun 1 Nov | Olten 15:55 | +2 min | +2 min |
| Sat 31 Oct | Olten 15:53 | 0 min | — |
| Fri 30 Oct | Olten 15:53 | 0 min | — |
| Thu 29 Oct | Olten 15:54 | 0 min | — |
| Wed 28 Oct | Olten 15:54 | +1 min | — |
| Tue 27 Oct | Olten 15:53 | 0 min | — |
| Mon 26 Oct | Olten 15:54 | 0 min | — |
| Sun 25 Oct | Olten 15:59 | +7 min | +7 min |
| Sat 24 Oct | Zofingen 16:04 | +20 min | +20 min |
| Fri 23 Oct | Olten 15:54 | +1 min | +1 min |
| Thu 22 Oct | Olten 15:53 | 0 min | — |
| Wed 21 Oct | Olten 15:52 | 0 min | — |
| Tue 20 Oct | Olten 15:53 | 0 min | — |
| Mon 19 Oct | Olten 15:53 | 0 min | — |
| Sun 18 Oct | Olten 15:53 | 0 min | — |
| Sat 17 Oct | Olten 15:54 | +1 min | — |
| Fri 16 Oct | Olten 15:55 | +1 min | +1 min |