S1 21170 Sursee – Zug
Alerts for train 21170
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: Wednesday 4 November 0 min
Next service: today 19:48 from Sursee · Thu 5 Nov
Last 30 days
Arrival delay at Zug, 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 17 Oct Max en route +3 min · last fix heading to Baar +3 min
- Tue 20 Oct Max en route +3 min · last fix heading to Zug +3 min
Distribution · 90 days
49 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 47
- 3–10 min 4% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=7
- 86% T n=7
- 100% W n=8
- 100% T n=7
- 100% F n=6
- 88% S n=8
- 100% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (21 stops).
Last 90 days, 49 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 |
|---|---|---|---|
| 19:48 | on time | +1 min | |
| 19:50 | ≈ on time | ≈ +1 min | |
| 19:52 | ≈ on time | ≈ +1 min | |
| 19:57 | ≈ on time | ≈ +1 min | |
| 20:01 | ≈ on time | ≈ +1 min | |
| 20:03 | ≈ on time | ≈ +1 min | |
| 20:06 | ≈ on time | ≈ +1 min | |
| 20:08 | ≈ on time | ≈ +1 min | |
| 20:15 / 20:21 | ≈ on time | ≈ +1 min | |
| 20:31 | ≈ on time | ≈ +1 min | |
| 20:33 | ≈ on time | ≈ +2 min | |
| 20:35 | ≈ on time | ≈ +2 min | |
| 20:37 | ≈ on time | ≈ +2 min | |
| 20:42 / 20:51 | ≈ on time | ≈ +2 min | |
| 20:54 | ≈ on time | ≈ +2 min | |
| 20:56 | ≈ on time | ≈ +2 min | |
| 20:57 | ≈ on time | ≈ +2 min | |
| 20:58 | ≈ on time | ≈ +2 min | |
| 21:00 | ≈ on time | ≈ +2 min | |
| 21:02 | ≈ +1 min | ≈ +2 min | |
| 21:05 | +1 min | +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 |
|---|---|---|---|
| Wed 4 Nov | Zug 21:04 | 0 min | — |
| Tue 3 Nov | Zug 21:04 | 0 min | — |
| Mon 2 Nov | Zug 21:08 | +2 min | +2 min |
| Sun 1 Nov | Baar 20:59 | +1 min | — |
| Sat 31 Oct | Baar 20:59 | +1 min | +1 min |
| Fri 30 Oct | Zug 21:06 | 0 min | — |
| Thu 29 Oct | Zug 21:07 | +1 min | — |
| Wed 28 Oct | Zug 21:08 | +2 min | +2 min |
| Tue 27 Oct | Zug 21:07 | +1 min | — |
| Mon 26 Oct | Zug 21:08 | +2 min | +2 min |
| Sun 25 Oct | Baar 20:59 | +2 min | +2 min |
| Sat 24 Oct | Baar 20:58 | 0 min | — |
| Fri 23 Oct | Zug 21:09 | +3 min | +3 min |
| Thu 22 Oct | Zug 21:06 | −1 min | — |
| Wed 21 Oct | Zug 21:05 | −1 min | — |
| Tue 20 Oct | Zug 21:09 | +3 min | +3 min |
| Mon 19 Oct | Zug 21:06 | 0 min | — |
| Sun 18 Oct | Baar 20:59 | +1 min | +1 min |
| Sat 17 Oct | Baar 21:01 | +3 min | +3 min |
| Fri 16 Oct | Zug 21:08 | +2 min | +2 min |
| Thu 15 Oct | Zug 21:06 | 0 min | — |
| Wed 14 Oct | Zug 21:07 | +1 min | — |
| Tue 13 Oct | Zug 21:08 | +1 min | +1 min |
| Mon 12 Oct | Zug 21:06 | +1 min | — |
| Sun 11 Oct | Baar 20:58 | 0 min | — |
| Sat 10 Oct | Baar 21:01 | +2 min | +2 min |
| Fri 9 Oct | Zug 21:07 | +1 min | — |
| Thu 8 Oct | Zug 21:07 | 0 min | — |
| Wed 7 Oct | Zug 21:07 | 0 min | — |
| Tue 6 Oct | Zug 21:07 | +1 min | +1 min |