RE7 4482 Luzern – Wolhusen
Alerts for train 4482
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line RE7.
Running now · updated 18:16
Position estimated from the timetable
Between Malters and Wolhusen +4 min
Estimated arrival at Wolhusen 18:17 18:13 · 56 km/h
- Luzern17:57
- Malters18:06
- Wolhusen18:13
Today it is running worse than usual: typical arrival delay is +1 min; 90% of the last 30 runs arrived on time.
Last 30 days
Arrival delay at Wolhusen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 12 Nov Max en route +4 min · last fix heading to Wolhusen +4 min
- Mon 9 Nov Max en route +3 min · last fix heading to Wolhusen +3 min
- Sun 25 Oct Max en route +3 min · last fix heading to Wolhusen +3 min
Distribution · 90 days
40 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 37
- 3–10 min 8% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 100% T n=6
- 100% W n=6
- 83% T n=6
- 100% F n=5
- 100% S n=5
- 83% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 40 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 |
|---|---|---|---|---|
| 17:57 | +1 min | +1 min | Passed | |
| 18:06 | ≈ +1 min | ≈ +2 min | Passed | |
| 18:13 | +1 min | +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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 12 Nov | Wolhusen 18:15 | +4 min | +4 min |
| Wed 11 Nov | Wolhusen 18:14 | +1 min | — |
| Tue 10 Nov | Wolhusen 18:14 | +2 min | +2 min |
| Mon 9 Nov | Wolhusen 18:17 | +3 min | +3 min |
| Sun 8 Nov | Wolhusen 18:14 | +1 min | — |
| Sat 7 Nov | Wolhusen 18:14 | +1 min | — |
| Fri 6 Nov | Wolhusen 18:14 | +3 min | +3 min |
| Thu 5 Nov | Wolhusen 18:14 | +1 min | +1 min |
| Wed 4 Nov | Wolhusen 18:14 | +1 min | — |
| Tue 3 Nov | Wolhusen 18:14 | +2 min | +2 min |
| Mon 2 Nov | Wolhusen 18:14 | +1 min | — |
| Sun 1 Nov | Wolhusen 18:16 | +2 min | +2 min |
| Sat 31 Oct | Wolhusen 18:15 | +1 min | — |
| Fri 30 Oct | Wolhusen 18:16 | +2 min | +2 min |
| Thu 29 Oct | Wolhusen 18:15 | +1 min | +2 min |
| Wed 28 Oct | Wolhusen 18:16 | +2 min | +2 min |
| Tue 27 Oct | Wolhusen 18:17 | +3 min | +3 min |
| Mon 26 Oct | Wolhusen 18:15 | +1 min | — |
| Sun 25 Oct | Wolhusen 18:17 | +3 min | +3 min |
| Sat 24 Oct | Wolhusen 18:14 | 0 min | — |
| Fri 23 Oct | Wolhusen 18:15 | +1 min | +1 min |
| Thu 22 Oct | Wolhusen 18:15 | +1 min | — |
| Wed 21 Oct | Wolhusen 18:17 | +3 min | +3 min |
| Tue 20 Oct | Wolhusen 18:15 | +1 min | — |
| Mon 19 Oct | Wolhusen 18:16 | +2 min | +2 min |
| Sun 18 Oct | Wolhusen 18:14 | +1 min | — |
| Sat 17 Oct | Wolhusen 18:15 | +2 min | +2 min |
| Fri 16 Oct | Wolhusen 18:16 | +1 min | +1 min |
| Thu 15 Oct | Wolhusen 18:15 | +1 min | +1 min |
| Wed 14 Oct | Wolhusen 18:15 | +2 min | +2 min |