S1 21176 Sursee – Luzern
Alerts for train 21176
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S1.
It has not run yet today
Last recorded run: Sunday 8 November −1 min
Next service: today 14:18 from Sursee · Mon 9 Nov
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
Worst days
- Tue 20 Oct Max en route +4 min · last fix heading to Baar +4 min
- Fri 21 Aug Max en route +4 min · last fix heading to Baar Lindenpark +4 min
- Fri 23 Oct Max en route +4 min · last fix heading to Baar +4 min
- Fri 9 Oct Max en route +4 min · last fix heading to Baar +4 min
Distribution · 90 days
56 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 1
- On time 91% · 51
- 3–10 min 7% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 86% T n=7
- 100% W n=6
- 100% T n=9
- 70% F n=10
- 100% S n=8
- 100% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 56 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 |
|---|---|---|---|
| 14:18 | on time | on time | |
| 14:20 | ≈ on time | ≈ +1 min | |
| 14:22 | ≈ on time | ≈ +1 min | |
| 14:26 / 14:27 | ≈ on time | ≈ +1 min | |
| 14:31 | ≈ on time | ≈ +1 min | |
| 14:33 | ≈ on time | ≈ +1 min | |
| 14:36 | ≈ on time | ≈ +2 min | |
| 14:38 | ≈ on time | ≈ +2 min | |
| 14:45 | 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 |
|---|---|---|---|
| Sun 8 Nov | Luzern 21:44 | −1 min | — |
| Sat 7 Nov | Luzern 21:44 | 0 min | — |
| Fri 6 Nov | Baar 22:29 | +1 min | +1 min |
| Thu 5 Nov | Baar 22:28 | 0 min | — |
| Wed 4 Nov | Baar 22:29 | 0 min | — |
| Tue 3 Nov | Baar 22:29 | 0 min | — |
| Mon 2 Nov | Baar 22:29 | 0 min | — |
| Sun 1 Nov | Baar 22:28 | 0 min | — |
| Sat 31 Oct | Baar 22:29 | +1 min | +1 min |
| Fri 30 Oct | Baar 22:28 | 0 min | — |
| Thu 29 Oct | Baar 22:29 | +1 min | — |
| Wed 28 Oct | Baar 22:29 | +1 min | — |
| Tue 27 Oct | Baar 22:28 | 0 min | — |
| Mon 26 Oct | Baar 22:28 | 0 min | — |
| Sun 25 Oct | Baar 22:29 | +1 min | +1 min |
| Sat 24 Oct | Baar 22:30 | +2 min | +2 min |
| Fri 23 Oct | Baar 22:32 | +4 min | +4 min |
| Thu 22 Oct | Baar 22:28 | 0 min | — |
| Wed 21 Oct | Baar 22:28 | 0 min | — |
| Tue 20 Oct | Baar 22:32 | +4 min | +4 min |
| Mon 19 Oct | Baar 22:28 | 0 min | — |
| Sun 18 Oct | Baar 22:28 | 0 min | — |
| Sat 17 Oct | Baar 22:30 | +2 min | +2 min |
| Fri 16 Oct | Baar 22:30 | +2 min | +2 min |
| Thu 15 Oct | Baar 22:28 | 0 min | — |
| Wed 14 Oct | Baar 22:28 | −1 min | — |
| Tue 13 Oct | Baar 22:29 | +1 min | — |
| Mon 12 Oct | Baar 22:27 | −1 min | — |
| Sun 11 Oct | Baar 22:28 | 0 min | — |
| Sat 10 Oct | Baar 22:28 | −1 min | — |