S10 12821 Zürich Selnau – Uetliberg

View line S10

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

✓ Today’s run finished

Today it reached Uetliberg at 11:35 0 min

  1. Zürich Selnau11:16
  2. Zürich Binz11:19
  3. Zürich Friesenberg11:21
  4. Zürich Triemli11:24
  5. Uitikon Waldegg11:28
  6. Ringlikon11:30
  7. Uetliberg11:35

Next service: tomorrow 11:16 from Zürich Selnau · Wed 18 Nov

Next departure 11:16 tomorrow · Zürich Selnau
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 8 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 10 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: +2 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

  • Sat 7 Nov Max en route +8 min · last fix heading to Uetliberg +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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