S9 18961 Rafz – Uster

View line S9

Rafz 15:45 → Uster 16:50 Daily 1 h 05 min · 18 stops SBB CFF FFS

Running now · updated 16:35

Position estimated from the timetable

Between Zürich Stadelhofen and Stettbach +1 min

Estimated arrival at Uster 16:51 · 63 km/h

  1. Rafz15:45
  2. Glattfelden15:53
  3. Oberglatt ZH16:05
  4. Zürich Oerlikon16:15
  5. Zürich Stadelhofen16:30
  6. Stettbach16:36
  7. Uster16:50

Today it is running no worse than usual: typical arrival delay is +1 min; 93% of the last 30 runs arrived on time.

On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
96%
47/49 runs under 3 min
RT coverage: 48 full · 1 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Uster, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 17 Nov Max en route +4 min · last fix heading to Uster +4 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Uster +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 47
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 88% T n=8
  • 100% W n=7
  • 100% T n=6
  • 86% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 49 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 10Today
15:45+1 min +1 minPassed
15:48≈ +1 min ≈ +1 minPassed
15:50 / 15:51≈ +1 min ≈ +1 minPassed
15:53 / 15:54≈ +1 min ≈ +1 minPassed
15:58≈ +1 min ≈ +1 minPassed
16:02≈ +1 min ≈ +1 minPassed
16:05≈ +1 min ≈ +1 minPassed
16:08≈ +1 min ≈ +1 minPassed
16:11 / 16:12≈ +1 min ≈ +1 minPassed
16:15 / 16:16≈ +1 min ≈ +1 minPassed
16:19≈ +1 min ≈ +1 minPassed
16:23 / 16:28≈ +1 min ≈ +1 minPassed
16:30 / 16:31≈ +1 min ≈ +2 minPassed
16:36≈ +1 min ≈ +2 minNext
16:39 / 16:40≈ +1 min ≈ +2 min
16:43≈ +1 min ≈ +2 min
16:45≈ +1 min ≈ +2 min
16:50+1 min +2 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
Wed 18 NovStettbach 16:34Partial coverage+1 min—
Tue 17 NovUster 16:54+4 min+4 min
Mon 16 NovUster 16:53+2 min+2 min
Sun 15 NovUster 16:49+1 min—
Sat 14 NovUster 16:52+1 min+1 min
Fri 13 NovUster 16:54+2 min+2 min
Thu 12 NovUster 16:52+1 min+1 min
Wed 11 NovUster 16:52+1 min+1 min
Tue 10 NovUster 16:49+1 min—
Mon 9 NovUster 16:53+3 min+3 min
Sun 8 NovUster 16:52+1 min—
Sat 7 NovUster 16:49+1 min—
Fri 6 NovUster 16:52+1 min—
Thu 5 NovUster 16:49+1 min—
Wed 4 NovUster 16:520 min—
Tue 3 NovUster 16:520 min—
Mon 2 NovUster 16:52+1 min—
Sun 1 NovUster 16:51+1 min—
Sat 31 OctUster 16:510 min—
Fri 30 OctUster 16:55+4 min+4 min
Thu 29 OctUster 16:510 min—
Wed 28 OctUster 16:520 min—
Tue 27 OctUster 16:53+2 min+2 min
Mon 26 OctUster 16:510 min—
Sun 25 OctUster 16:52+1 min+1 min
Sat 24 OctUster 16:51+1 min—
Fri 23 OctUster 16:53+1 min+1 min
Thu 22 OctUster 16:52+1 min—
Wed 21 OctUster 16:52+1 min—
Tue 20 OctUster 16:53+2 min+2 min