S10 12797 Zürich Selnau – Uetliberg

View line S10

Zürich Selnau 09:16 → Uetliberg 09:35 Daily 0 h 19 min · 8 stops SZU

✓ Today’s run finished

Today it reached Uetliberg at 09:35 0 min

  1. Zürich Selnau09:16
  2. Zürich Binz09:19
  3. Zürich Friesenberg09:21
  4. Zürich Triemli09:24
  5. Uitikon Waldegg09:28
  6. Ringlikon09:30
  7. Uetliberg09:35

Next service: tomorrow 09:16 from Zürich Selnau · Fri 6 Nov

Next departure 09:16 tomorrow · Zürich Selnau
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 35 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

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 +5 min · last fix heading to Uetliberg +3 min

Distribution · 90 days

35 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 97% · 34
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 100% W n=6
  • 100% T n=5
  • 80% F n=5
  • 100% S n=3
  • 100% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 35 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.

StopSched.Usually 9 days in 10
09:16on time on time
09:19≈ on time ≈ on time
09:21≈ on time ≈ on time
09:22≈ on time ≈ on time
09:24≈ on time ≈ on time
09:28≈ on time ≈ on time
09:30≈ on time ≈ on time
09:35on 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

DateLast stopFinalMax
Thu 5 NovUetliberg 09:340 min—
Wed 4 NovUetliberg 09:340 min—
Tue 3 NovUetliberg 09:340 min—
Mon 2 NovUetliberg 09:37+1 min—
Sun 1 NovUetliberg 09:350 min—
Sat 31 OctUetliberg 09:360 min—
Fri 30 OctUetliberg 09:360 min—
Thu 29 OctUetliberg 09:36No data—
Wed 28 OctUetliberg 09:350 min—
Tue 27 OctUetliberg 09:37+1 min—
Mon 26 OctZürich Selnau 11:010 min—
Fri 23 OctUetliberg 09:360 min—
Thu 22 OctUetliberg 09:360 min—
Wed 21 OctUetliberg 09:350 min—
Tue 20 OctUetliberg 09:36−1 min—
Mon 19 OctUetliberg 09:350 min—
Sun 18 OctUetliberg 09:360 min—
Sat 17 OctUetliberg 09:360 min—
Fri 16 OctUetliberg 09:35−1 min—
Thu 15 OctUetliberg 09:350 min—
Wed 14 OctUetliberg 09:350 min—
Tue 13 OctUetliberg 09:36−1 min—
Mon 12 OctUetliberg 09:350 min—
Sun 11 OctUetliberg 09:360 min—
Sat 10 OctUetliberg 09:370 min—
Fri 9 OctUetliberg 09:350 min—
Thu 8 OctUetliberg 09:37+1 min—
Wed 7 OctUetliberg 09:360 min—
Tue 6 OctUetliberg 09:350 min—
Mon 5 OctUetliberg 09:370 min—