S1 22144 Rotkreuz – Baar
Alerts for train 22144
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.
✓ Today’s run finished
Today, last fix heading to Baar at 14:44 No data
- Rotkreuz14:23
- Hünenberg Zythus14:27
- Cham14:29
- Zug Chollermüli14:32
- Zug14:37
- Baar Lindenpark14:38
- Baar14:42
Next service: tomorrow 14:23 from Rotkreuz · Fri 13 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
- Wed 21 Oct Max en route +5 min · last fix heading to Baar +5 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 23
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=6
- 83% W n=6
- 100% T n=1
- 100% F n=5
- 100% S n=5
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 24 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:23 | on time | +1 min | |
| 14:26 | ≈ on time | ≈ +1 min | |
| 14:27 | ≈ on time | ≈ +1 min | |
| 14:29 | ≈ on time | ≈ +1 min | |
| 14:30 | ≈ on time | ≈ +1 min | |
| 14:32 | ≈ on time | ≈ +1 min | |
| 14:34 | ≈ on time | ≈ +1 min | |
| 14:37 | ≈ +1 min | ≈ +1 min | |
| 14:38 | ≈ +1 min | ≈ +2 min | |
| 14:40 | ≈ +1 min | ≈ +2 min | |
| 14:42 | +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 |
|---|---|---|---|
| Thu 12 Nov | Baar 14:44 | No data | — |
| Wed 11 Nov | Baar 14:44 | +1 min | — |
| Tue 10 Nov | Baar 14:43 | 0 min | — |
| Mon 9 Nov | Baar 14:43 | No data | — |
| Sat 7 Nov | Baar 14:44 | +2 min | +2 min |
| Fri 6 Nov | Baar 14:43 | 0 min | — |
| Thu 5 Nov | Baar 14:43 | No data | — |
| Wed 4 Nov | Baar 14:44 | +1 min | +1 min |
| Tue 3 Nov | Baar 14:44 | +1 min | — |
| Mon 2 Nov | Baar 14:43 | No data | — |
| Sat 31 Oct | Baar 14:43 | 0 min | — |
| Fri 30 Oct | Baar 14:44 | +1 min | — |
| Thu 29 Oct | Baar 14:43 | No data | — |
| Wed 28 Oct | Baar 14:44 | +1 min | +1 min |
| Tue 27 Oct | Baar 14:45 | +1 min | +1 min |
| Mon 26 Oct | Baar 14:43 | No data | — |
| Sat 24 Oct | Baar 14:43 | 0 min | — |
| Fri 23 Oct | Baar 14:44 | +1 min | +2 min |
| Thu 22 Oct | Baar 14:43 | No data | — |
| Wed 21 Oct | Baar 14:48 | +5 min | +5 min |
| Tue 20 Oct | Baar 14:43 | 0 min | — |
| Mon 19 Oct | Baar 14:43 | No data | — |
| Sat 17 Oct | Baar 14:45 | +2 min | +2 min |
| Fri 16 Oct | Baar 14:44 | +1 min | — |
| Thu 15 Oct | Baar 14:43 | No data | — |
| Wed 14 Oct | Baar 14:43 | 0 min | — |
| Tue 13 Oct | Baar 14:44 | 0 min | — |
| Mon 12 Oct | Baar 14:43 | No data | — |
| Sat 10 Oct | Baar 14:44 | +1 min | — |
| Fri 9 Oct | Baar 14:43 | 0 min | — |