S9 18957 Rafz → Uster

View line S9

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

S9 18957 Rafz–Uster: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 21:10 (GMT+1).

✓ Today’s run finished

Today it reached Uster at 15:51 +1 min

  1. Rafz14:45
  2. Glattfelden14:53
  3. Oberglatt ZH15:05
  4. Zürich Oerlikon15:15
  5. Zürich HB15:23
  6. Dübendorf15:39
  7. Uster15:50

Next service: tomorrow 14:45 from Rafz · Sun 22 Nov

Next departure 14:45 tomorrow · Rafz
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
50/50 runs under 3 min
RT coverage: 50 full · 0 partial · 0 no data
Typical delay
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 50
  • 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=7
  • 100% W n=8
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

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