S10 12785 Zürich Selnau – Uetliberg

View line S10

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 08:16 from Zürich Selnau · Wed 18 Nov

Next departure 08:16 today · Zürich Selnau
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
100%
47/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 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

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

  • Early 2% · 1
  • On time 98% · 46
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% T n=7
  • 100% F n=7
  • 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, 47 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
08:16on time on time
08:19≈ on time ≈ on time
08:21≈ on time ≈ on time
08:22≈ on time ≈ on time
08:24≈ on time ≈ on time
08:28≈ on time ≈ on time
08:30≈ on time ≈ on time
08: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
Tue 17 NovUetliberg 08:340 min—
Mon 16 NovUetliberg 08:37+1 min+1 min
Sun 15 NovUetliberg 08:340 min—
Sat 14 NovUetliberg 08:340 min—
Fri 13 NovUetliberg 08:340 min—
Thu 12 NovUetliberg 08:370 min—
Wed 11 NovUetliberg 08:340 min—
Tue 10 NovUetliberg 08:38+2 min+2 min
Mon 9 NovUetliberg 08:340 min—
Sun 8 NovUetliberg 08:370 min—
Sat 7 NovUetliberg 08:340 min—
Fri 6 NovUetliberg 08:340 min—
Thu 5 NovUetliberg 08:340 min—
Wed 4 NovUetliberg 08:340 min—
Tue 3 NovUetliberg 08:37+1 min—
Mon 2 NovUetliberg 08:370 min—
Sun 1 NovUetliberg 08:360 min—
Sat 31 OctUetliberg 08:360 min—
Fri 30 OctUetliberg 08:360 min—
Thu 29 OctUetliberg 08:350 min—
Wed 28 OctUetliberg 08:370 min—
Tue 27 OctUetliberg 08:36+1 min—
Mon 26 OctUetliberg 08:36−1 min—
Fri 23 OctUetliberg 08:360 min—
Thu 22 OctUetliberg 08:370 min—
Wed 21 OctUetliberg 08:360 min—
Tue 20 OctUetliberg 08:360 min—
Mon 19 OctUetliberg 08:350 min—
Sun 18 OctUetliberg 08:37+1 min—
Sat 17 OctUetliberg 08:36−1 min—