S10 12849 Zürich Selnau – Uetliberg

View line S10

Zürich Selnau 13:36 → Uetliberg 14:00 Daily 0 h 24 min · 8 stops SZU

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 13:36 from Zürich Selnau · Mon 16 Nov

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

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 98% · 45
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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