S10 12809 Zürich Selnau – Uetliberg

View line S10

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

✓ Today’s run finished

Today it reached Uetliberg at 16:35 0 min

  1. Zürich Selnau16:16
  2. Zürich Binz16:19
  3. Zürich Friesenberg16:21
  4. Zürich Triemli16:24
  5. Uitikon Waldegg16:28
  6. Ringlikon16:30
  7. Uetliberg16:35

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

Next departure 16: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
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 41
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 41 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
16:16on time on time
16:19≈ on time ≈ on time
16:21≈ on time ≈ on time
16:22≈ on time ≈ on time
16:24≈ on time ≈ on time
16:28≈ on time ≈ on time
16:30≈ on time ≈ +1 min
16: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 12 NovUetliberg 10:340 min—
Wed 11 NovUetliberg 10:340 min—
Tue 10 NovUetliberg 10:37+1 min—
Mon 9 NovUetliberg 10:340 min—
Sun 8 NovUetliberg 10:370 min—
Sat 7 NovUetliberg 10:340 min—
Fri 6 NovUetliberg 10:340 min—
Thu 5 NovUetliberg 10:340 min—
Wed 4 NovUetliberg 10:37+1 min+1 min
Tue 3 NovUetliberg 10:340 min—
Mon 2 NovUetliberg 10:370 min—
Sun 1 NovUetliberg 10:37+1 min+1 min
Sat 31 OctUetliberg 10:37+1 min—
Fri 30 OctUetliberg 10:37+1 min—
Thu 29 OctUetliberg 10:36No data—
Wed 28 OctUetliberg 10:360 min—
Tue 27 OctUetliberg 10:370 min—
Mon 26 OctZürich Selnau 11:010 min—
Fri 23 OctUetliberg 10:360 min—
Thu 22 OctUetliberg 10:360 min—
Wed 21 OctUetliberg 10:37+1 min+1 min
Tue 20 OctUetliberg 10:36+1 min—
Mon 19 OctUetliberg 10:360 min—
Sun 18 OctUetliberg 10:360 min—
Sat 17 OctUetliberg 10:360 min—
Fri 16 OctUetliberg 10:350 min—
Thu 15 OctUetliberg 10:37+1 min—
Wed 14 OctUetliberg 10:350 min—
Tue 13 OctUetliberg 10:38+1 min+1 min
Mon 12 OctUetliberg 10:350 min—