S10 12837 Zürich Selnau – Uetliberg

View line S10

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

It has not run yet today

Last recorded run: Monday 16 November No data

Next service: today 12:36 from Zürich Selnau · Tue 17 Nov

Next departure 12:36 today · Zürich Selnau
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 9 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 11 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

  • Mon 31 Aug Max en route +26 min · last fix heading to Uetliberg +26 min

Distribution · 90 days

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

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

On-time by weekday

  • 67% M n=3
  • 100% T n=7
  • 100% W n=6
  • 100% T n=2
  • 100% F n=8
  • 100% S n=6
  • 100% S n=8

Stops and timetable

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

Last 90 days, 40 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
12:36on time on time
12:39≈ on time ≈ on time
12:41≈ on time ≈ on time
12:42≈ on time ≈ on time
12:44≈ on time ≈ on time
12:48≈ on time ≈ on time
12:50≈ on time ≈ +1 min
12: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
Mon 16 NovUetliberg 12:54No data—
Sun 15 NovUetliberg 12:590 min—
Sat 14 NovUetliberg 12:590 min—
Fri 13 NovUetliberg 12:540 min—
Thu 12 NovUetliberg 12:54No data—
Wed 11 NovUetliberg 12:540 min—
Tue 10 NovUetliberg 12:570 min—
Mon 9 NovUetliberg 12:54No data—
Sun 8 NovUetliberg 13:020 min—
Sat 7 NovUetliberg 12:590 min—
Fri 6 NovUetliberg 12:57+1 min+1 min
Thu 5 NovUetliberg 12:54No data—
Wed 4 NovUetliberg 12:57+1 min—
Tue 3 NovUetliberg 12:57+1 min—
Mon 2 NovUetliberg 12:54No data—
Sun 1 NovUetliberg 13:010 min—
Sat 31 OctUetliberg 13:010 min—
Fri 30 OctUetliberg 12:560 min—
Thu 29 OctUetliberg 12:56No data—
Wed 28 OctUetliberg 12:550 min—
Tue 27 OctUetliberg 12:58+1 min+1 min
Mon 26 OctUetliberg 12:56No data—
Fri 23 OctUetliberg 12:560 min—
Thu 22 OctUetliberg 12:56No data—
Wed 21 OctUetliberg 12:560 min—
Tue 20 OctUetliberg 12:57+1 min—
Mon 19 OctUetliberg 12:56No data—
Sun 18 OctUetliberg 13:010 min—
Sat 17 OctUetliberg 13:010 min—
Fri 16 OctUetliberg 12:550 min—