S9 18945 Rafz – Uster

View line S9

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

✓ Today’s run finished

Today, last fix heading to Uster at 12:49 No data

  1. Rafz11:45
  2. Glattfelden11:53
  3. Oberglatt ZH12:05
  4. Zürich Oerlikon12:15
  5. Zürich HB12:23
  6. Dübendorf12:39
  7. Uster12:50

Next service: tomorrow 11:45 from Rafz · Fri 6 Nov

Next departure 11:45 tomorrow · Rafz
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 33 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 1 Nov Max en route +5 min · last fix heading to Uster +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Uster +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 80% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=6
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

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