S9 18949 Rafz – Uster
Alerts for train 18949
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S9.
It has not run yet today
Last recorded run: Wednesday 4 November +7 min
Next service: today 12:45 from Rafz · Thu 5 Nov
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
- Wed 4 Nov Max en route +7 min · last fix heading to Uster +7 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 25
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=5
- 80% W n=5
- 100% T n=2
- 100% F n=4
- 100% S n=4
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (18 stops).
Last 90 days, 26 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 12:45 | +1 min | +1 min | |
| 12:48 | ≈ +1 min | ≈ +1 min | |
| 12:50 / 12:51 | ≈ +1 min | ≈ +1 min | |
| 12:53 / 12:54 | ≈ +1 min | ≈ +1 min | |
| 12:58 | ≈ +1 min | ≈ +1 min | |
| 13:02 | ≈ on time | ≈ +1 min | |
| 13:05 | ≈ on time | ≈ +1 min | |
| 13:08 | ≈ on time | ≈ +1 min | |
| 13:11 / 13:12 | ≈ on time | ≈ +1 min | |
| 13:15 / 13:16 | ≈ on time | ≈ +1 min | |
| 13:19 | ≈ on time | ≈ +1 min | |
| 13:23 / 13:28 | ≈ on time | ≈ +1 min | |
| 13:30 / 13:31 | ≈ on time | ≈ +1 min | |
| 13:36 | ≈ on time | ≈ +1 min | |
| 13:39 / 13:40 | ≈ on time | ≈ +1 min | |
| 13:43 | ≈ on time | ≈ +1 min | |
| 13:45 | ≈ on time | ≈ +1 min | |
| 13:50 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Uster 13:58 | +7 min | +7 min |
| Tue 3 Nov | Uster 13:52 | +1 min | — |
| Mon 2 Nov | Uster 13:49 | No data | — |
| Sun 1 Nov | Uster 13:51 | 0 min | — |
| Sat 31 Oct | Uster 13:51 | 0 min | — |
| Fri 30 Oct | Uster 13:51 | 0 min | — |
| Thu 29 Oct | Uster 13:51 | No data | — |
| Wed 28 Oct | Uster 13:51 | 0 min | — |
| Tue 27 Oct | Uster 13:51 | 0 min | — |
| Mon 26 Oct | Uster 13:51 | No data | — |
| Sun 25 Oct | Uster 13:51 | 0 min | — |
| Sat 24 Oct | Uster 13:52 | +1 min | — |
| Fri 23 Oct | Uster 13:51 | 0 min | — |
| Thu 22 Oct | Uster 13:51 | No data | — |
| Wed 21 Oct | Uster 13:52 | +1 min | +1 min |
| Tue 20 Oct | Uster 13:52 | +1 min | +1 min |
| Mon 19 Oct | Uster 13:51 | No data | — |
| Sun 18 Oct | Uster 13:51 | 0 min | — |
| Sat 17 Oct | Uster 13:51 | 0 min | — |
| Fri 16 Oct | Uster 13:53 | +2 min | +2 min |
| Thu 15 Oct | Uster 13:52 | +1 min | — |
| Wed 14 Oct | Uster 13:51 | 0 min | — |
| Tue 13 Oct | Uster 13:52 | +1 min | — |
| Mon 12 Oct | Uster 13:51 | No data | — |
| Sun 11 Oct | Uster 13:52 | 0 min | — |
| Sat 10 Oct | Uster 13:52 | +1 min | — |
| Fri 9 Oct | Uster 13:50 | −1 min | — |
| Thu 8 Oct | Uster 13:52 | +1 min | — |
| Wed 7 Oct | Uster 13:52 | +1 min | — |
| Tue 6 Oct | Uster 13:51 | 0 min | — |