S1 22162 Rotkreuz → Baar
Alerts for train 22162
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.
S1 22162 Rotkreuz–Baar: final delay under 3 min on 24 of its 25 runs with data in the last 30 days (96%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 18:31 (GMT+1).
An alert on this phone or computer when the 22162 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Friday 20 November +1 min
Next service: today 18:39 from Rotkreuz · Sat 21 Nov
Last 30 days
Arrival delay at Baar, 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 19 Nov Max en route +3 min · last fix heading to Baar +3 min
Distribution · 90 days
42 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 5% · 2
- On time 93% · 39
- 3–10 min 2% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=7
- 100% T n=7
- 100% W n=7
- 86% T n=7
- 100% F n=7
- 100% S n=7
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 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 |
|---|---|---|---|
| 18:39 | on time | on time | |
| 18:42 | ≈ on time | ≈ +1 min | |
| 18:44 | ≈ on time | ≈ +1 min | |
| 18:45 | ≈ on time | ≈ +1 min | |
| 18:47 | ≈ +1 min | ≈ +1 min | |
| 18:49 | ≈ +1 min | ≈ +1 min | |
| 18:51 | ≈ +1 min | ≈ +1 min | |
| 18:53 | ≈ +1 min | ≈ +2 min | |
| 18:54 | ≈ +1 min | ≈ +2 min | |
| 18:57 | +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 |
|---|---|---|---|
| Fri 20 Nov | Baar 18:59 | +1 min | +1 min |
| Thu 19 Nov | Baar 18:59 | +3 min | +3 min |
| Wed 18 Nov | Baar 18:58 | 0 min | — |
| Tue 17 Nov | Baar 18:59 | +1 min | — |
| Mon 16 Nov | Baar 18:57 | −1 min | — |
| Sat 14 Nov | Baar 18:58 | −1 min | — |
| Fri 13 Nov | Baar 18:58 | −1 min | — |
| Thu 12 Nov | Baar 18:59 | +2 min | +2 min |
| Wed 11 Nov | Baar 18:59 | +2 min | +2 min |
| Tue 10 Nov | Baar 18:59 | +2 min | +2 min |
| Mon 9 Nov | Baar 18:59 | +1 min | +1 min |
| Sat 7 Nov | Baar 18:57 | 0 min | — |
| Fri 6 Nov | Baar 18:58 | +1 min | — |
| Thu 5 Nov | Baar 18:58 | 0 min | — |
| Wed 4 Nov | Baar 18:59 | +3 min | +3 min |
| Tue 3 Nov | Baar 18:59 | +1 min | — |
| Mon 2 Nov | Baar 18:59 | +2 min | +2 min |
| Sat 31 Oct | Baar 18:59 | +1 min | +1 min |
| Fri 30 Oct | Baar 19:00 | +2 min | +2 min |
| Thu 29 Oct | Baar 18:59 | +1 min | — |
| Wed 28 Oct | Baar 18:58 | 0 min | — |
| Tue 27 Oct | Baar 18:59 | 0 min | — |
| Mon 26 Oct | Baar 18:59 | +1 min | +1 min |
| Sat 24 Oct | Baar 18:58 | 0 min | — |
| Fri 23 Oct | Baar 18:59 | +1 min | +1 min |
| Thu 22 Oct | Baar 18:57 | −1 min | — |
| Wed 21 Oct | Baar 19:00 | +2 min | +2 min |
| Tue 20 Oct | Baar 19:00 | +2 min | +2 min |
| Mon 19 Oct | Baar 18:59 | +2 min | +2 min |
| Sat 17 Oct | Baar 18:58 | 0 min | — |