S10 12777 Zürich Selnau – Uetliberg

View line S10

Zürich Selnau 12:56 → Uetliberg 13:15 Daily 0 h 19 min · 8 stops SZU

It has not run yet today

Last recorded run: Thursday 19 November −1 min

Next service: today 12:56 from Zürich Selnau · Fri 20 Nov

Next departure 12:56 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%
53/53 runs under 3 min
RT coverage: 53 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

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

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

On-time by weekday

  • 100% M n=9
  • 100% T n=9
  • 100% W n=8
  • 100% T n=9
  • 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, 53 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:56on time on time
12:59≈ on time ≈ on time
13:01≈ on time ≈ on time
13:02≈ on time ≈ on time
13:04≈ on time ≈ on time
13:08≈ on time ≈ on time
13:10≈ on time ≈ on time
13:15on 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 19 NovUetliberg 07:54−1 min—
Wed 18 NovUetliberg 07:540 min—
Tue 17 NovUetliberg 07:540 min—
Mon 16 NovUetliberg 07:58+2 min+2 min
Sun 15 NovUetliberg 07:57+1 min—
Sat 14 NovUetliberg 07:540 min—
Fri 13 NovUetliberg 07:540 min—
Thu 12 NovUetliberg 07:570 min—
Wed 11 NovUetliberg 07:540 min—
Tue 10 NovUetliberg 07:58+2 min+2 min
Mon 9 NovUetliberg 07:540 min—
Sun 8 NovUetliberg 07:540 min—
Sat 7 NovUetliberg 07:540 min—
Fri 6 NovUetliberg 07:540 min—
Thu 5 NovUetliberg 07:540 min—
Wed 4 NovUetliberg 07:540 min—
Tue 3 NovUetliberg 07:540 min—
Mon 2 NovUetliberg 07:57+1 min+1 min
Sun 1 NovUetliberg 07:560 min—
Sat 31 OctUetliberg 07:57+1 min—
Fri 30 OctUetliberg 07:560 min—
Thu 29 OctUetliberg 07:560 min—
Wed 28 OctUetliberg 07:560 min—
Tue 27 OctUetliberg 07:57+1 min—
Mon 26 OctUetliberg 07:570 min—
Fri 23 OctUetliberg 07:560 min—
Thu 22 OctUetliberg 07:560 min—
Wed 21 OctUetliberg 07:56−1 min—
Tue 20 OctUetliberg 07:58+1 min+1 min
Mon 19 OctUetliberg 07:560 min—