S9 18953 Rafz – Uster

View line S9

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

✓ Today’s run finished

Today it reached Uster at 14:52 +2 min

  1. Rafz13:45
  2. Glattfelden13:53
  3. Oberglatt ZH14:05
  4. Zürich Oerlikon14:15
  5. Zürich HB14:23
  6. Dübendorf14:39
  7. Uster14:50

Next service: tomorrow 13:45 from Rafz · Sat 21 Nov

Next departure 13:45 tomorrow · Rafz
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 4 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 4 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 20 Oct Max en route +5 min · last fix heading to Uster +5 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 98% · 48
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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