S10 12845 Zürich Selnau – Uetliberg
Alerts for train 12845
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S10.
✓ Today’s run finished
Today it reached Uetliberg at 13:41 +1 min
- Zürich Selnau13:16
- Zürich Binz13:19
- Zürich Friesenberg13:21
- Zürich Triemli13:24
- Uitikon Waldegg13:33
- Ringlikon13:35
- Uetliberg13:40
Next service: tomorrow 13:16 from Zürich Selnau · Mon 16 Nov
Last 30 days
Arrival delay at Uetliberg, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 21 Aug Max en route +3 min · last fix heading to Uetliberg +3 min
Distribution · 90 days
42 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 1
- On time 95% · 40
- 3–10 min 2% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=6
- 100% W n=6
- 100% T n=4
- 89% F n=9
- 100% S n=7
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 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 |
|---|---|---|---|
| 13:16 | on time | on time | |
| 13:19 | ≈ on time | ≈ on time | |
| 13:21 | ≈ on time | ≈ on time | |
| 13:22 | ≈ on time | ≈ on time | |
| 13:24 / 13:29 | ≈ on time | ≈ on time | |
| 13:33 | ≈ on time | ≈ on time | |
| 13:35 | ≈ on time | ≈ +1 min | |
| 13:40 | on time | +1 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 15 Nov | Uetliberg 13:42 | +1 min | — |
| Sat 14 Nov | Uetliberg 13:39 | 0 min | — |
| Fri 13 Nov | Uetliberg 13:34 | 0 min | — |
| Thu 12 Nov | Uetliberg 13:34 | No data | — |
| Wed 11 Nov | Uetliberg 13:34 | 0 min | — |
| Tue 10 Nov | Uetliberg 13:37 | 0 min | — |
| Mon 9 Nov | Uetliberg 13:34 | No data | — |
| Sun 8 Nov | Uetliberg 13:43 | +1 min | +1 min |
| Sat 7 Nov | Uetliberg 13:42 | +1 min | — |
| Fri 6 Nov | Uetliberg 13:34 | 0 min | — |
| Thu 5 Nov | Uetliberg 13:34 | No data | — |
| Wed 4 Nov | Uetliberg 13:34 | 0 min | — |
| Tue 3 Nov | Uetliberg 13:34 | 0 min | — |
| Mon 2 Nov | Uetliberg 13:34 | No data | — |
| Sun 1 Nov | Uetliberg 13:41 | +1 min | — |
| Sat 31 Oct | Uetliberg 13:42 | +1 min | — |
| Fri 30 Oct | Uetliberg 13:36 | 0 min | — |
| Thu 29 Oct | Uetliberg 13:36 | No data | — |
| Wed 28 Oct | Uetliberg 13:36 | 0 min | — |
| Tue 27 Oct | Uetliberg 13:37 | +1 min | — |
| Mon 26 Oct | Uetliberg 13:36 | No data | — |
| Fri 23 Oct | Uetliberg 13:35 | −1 min | — |
| Thu 22 Oct | Uetliberg 13:36 | No data | — |
| Wed 21 Oct | Uetliberg 13:36 | 0 min | — |
| Tue 20 Oct | Uetliberg 13:37 | 0 min | — |
| Mon 19 Oct | Uetliberg 13:36 | No data | — |
| Sun 18 Oct | Uetliberg 13:41 | 0 min | — |
| Sat 17 Oct | Uetliberg 13:41 | 0 min | — |
| Fri 16 Oct | Uetliberg 13:37 | 0 min | — |
| Thu 15 Oct | Uetliberg 13:36 | No data | — |