Train NS 8932 Utrecht Centraal – Woerden
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 10:35 from Utrecht Centraal · Thu 5 Nov
Last 30 days
Arrival delay at Woerden, 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
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 13
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=3
- 100% W n=4
- 100% T n=2
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 10:35 | on time | on time | |
| 10:39 | — | — | |
| 10:41 | — | — | |
| 10:45 | — | — | |
| 10:51 | — | — |
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 | Vleuten 10:59Partial coverage | 0 min | — |
| Tue 3 Nov | Vleuten 10:59Partial coverage | 0 min | — |
| Mon 2 Nov | Vleuten 10:59 | No data | — |
| Fri 30 Oct | Vleuten 10:59 | No data | — |
| Thu 29 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Wed 28 Oct | Vleuten 11:09Partial coverage | 0 min | — |
| Tue 27 Oct | Vleuten 10:59 | No data | — |
| Mon 26 Oct | Vleuten 10:59 | No data | — |
| Fri 23 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Thu 22 Oct | Vleuten 11:00 | No data | — |
| Wed 21 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Tue 20 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Fri 16 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Thu 15 Oct | Vleuten 10:59 | No data | — |
| Wed 14 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Tue 13 Oct | Vleuten 10:59 | No data | — |
| Mon 12 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Fri 9 Oct | Vleuten 10:59Partial coverage | 0 min | — |
| Thu 8 Oct | Vleuten 11:00Partial coverage | +1 min | +1 min |
| Wed 7 Oct | Utrecht Leidsche Rijn 12:00 | No data | — |
| Tue 6 Oct | Vleuten 10:59Partial coverage | +1 min | +1 min |
| Mon 5 Oct | Vleuten 10:59 | No data | — |
| Fri 2 Oct | Vleuten 10:59 | No data | — |
| Thu 1 Oct | Vleuten 10:59 | No data | — |
| Wed 30 Sept | Vleuten 11:00 | No data | — |
| Tue 29 Sept | Vleuten 10:59 | No data | — |
| Mon 28 Sept | Vleuten 10:59 | No data | — |
| Fri 25 Sept | Vleuten 10:59 | No data | — |
| Thu 24 Sept | Vleuten 10:59 | No data | — |
| Wed 23 Sept | Vleuten 10:59 | No data | — |