S10 12765 Zürich Selnau – Uetliberg

View line S10

Zürich Selnau 06:36 → Uetliberg 06:55 Daily 0 h 19 min · 8 stops SZU

Running now · updated 06:44

Position estimated from the timetable

Between Zürich Triemli and Uitikon Waldegg 0 min

Estimated arrival at Uetliberg 06:55 · 23 km/h

  1. Zürich Selnau06:36
  2. Zürich Binz06:39
  3. Zürich Friesenberg06:41
  4. Zürich Triemli06:44
  5. Uitikon Waldegg06:48
  6. Ringlikon06:50
  7. Uetliberg06:55

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 28 runs arrived on time.

On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 27 full · 1 partial · 0 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 45 full · 1 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: +1 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

  • Wed 2 Sept Max en route +6 min · last fix heading to Uetliberg +6 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 96% · 44
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=6
  • 86% W n=7
  • 100% T n=8
  • 100% F n=6
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 46 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 10Today
06:36on time on timePassed
06:39≈ on time ≈ on timePassed
06:41≈ on time ≈ on timePassed
06:42≈ on time ≈ on timePassed
06:44≈ on time ≈ +1 minPassed
06:48≈ on time ≈ +1 minNext
06:50≈ on time ≈ +1 min
06:55on 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 12 NovZürich Friesenberg 06:39Partial coverage0 min—
Wed 11 NovUetliberg 06:540 min—
Tue 10 NovUetliberg 06:58+2 min+2 min
Mon 9 NovUetliberg 06:57+1 min—
Sun 8 NovUetliberg 06:57+1 min+1 min
Sat 7 NovUetliberg 06:540 min—
Fri 6 NovUetliberg 06:570 min—
Thu 5 NovUetliberg 06:540 min—
Wed 4 NovUetliberg 06:540 min—
Tue 3 NovUetliberg 06:58+2 min+2 min
Mon 2 NovUetliberg 06:58+2 min+2 min
Sun 1 NovUetliberg 06:560 min—
Sat 31 OctUetliberg 06:57+1 min—
Fri 30 OctUetliberg 06:560 min—
Thu 29 OctUetliberg 06:550 min—
Wed 28 OctUetliberg 06:550 min—
Tue 27 OctUetliberg 06:57+1 min—
Mon 26 OctUetliberg 06:570 min—
Fri 23 OctUetliberg 06:560 min—
Thu 22 OctUetliberg 06:550 min—
Wed 21 OctUetliberg 06:56+1 min—
Tue 20 OctUetliberg 06:58+1 min+1 min
Mon 19 OctUetliberg 06:570 min—
Sun 18 OctUetliberg 06:58+1 min+1 min
Sat 17 OctUetliberg 06:550 min—
Fri 16 OctUetliberg 06:550 min—
Thu 15 OctUetliberg 06:570 min—
Wed 14 OctUetliberg 06:560 min—
Tue 13 OctUetliberg 06:57+2 min+2 min
Mon 12 OctUetliberg 06:550 min—