S10 12913 Zürich Selnau – Uetliberg

View line S10

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

It has not run yet today

Last recorded run: Saturday 14 November +2 min

Next service: today 18:56 from Zürich Selnau · Sun 15 Nov

Next departure 18: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
0min
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 4% · 2
  • On time 96% · 51
  • 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=8
  • 100% W n=9
  • 100% T n=7
  • 100% F n=9
  • 100% S n=7
  • 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
18:56on time on time
18:59≈ on time ≈ on time
19:01≈ on time ≈ on time
19:02≈ on time ≈ on time
19:04≈ on time ≈ on time
19:08≈ on time ≈ on time
19:10≈ on time ≈ on time
19:15on time on time

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
Sat 14 NovUetliberg 19:17+2 min+2 min
Fri 13 NovUetliberg 19:170 min—
Thu 12 NovUetliberg 19:130 min—
Wed 11 NovUetliberg 19:140 min—
Tue 10 NovUetliberg 19:140 min—
Mon 9 NovUetliberg 19:140 min—
Sun 8 NovUetliberg 19:140 min—
Sat 7 NovUetliberg 19:140 min—
Fri 6 NovUetliberg 19:140 min—
Thu 5 NovUetliberg 19:140 min—
Wed 4 NovUetliberg 19:140 min—
Tue 3 NovUetliberg 19:170 min—
Mon 2 NovUetliberg 19:170 min—
Sun 1 NovUetliberg 19:140 min—
Sat 31 OctUetliberg 19:16+1 min—
Fri 30 OctUetliberg 19:17+1 min+1 min
Thu 29 OctUetliberg 19:17+1 min—
Wed 28 OctUetliberg 19:160 min—
Tue 27 OctUetliberg 19:150 min—
Mon 26 OctUetliberg 19:16−1 min—
Fri 23 OctUetliberg 19:160 min—
Thu 22 OctUetliberg 19:170 min—
Wed 21 OctUetliberg 19:15−1 min—
Tue 20 OctUetliberg 19:160 min—
Mon 19 OctUetliberg 19:15−1 min—
Sun 18 OctUetliberg 19:150 min—
Sat 17 OctUetliberg 19:160 min—
Fri 16 OctUetliberg 19:170 min—
Thu 15 OctUetliberg 19:16+1 min—
Wed 14 OctUetliberg 19:15−1 min—