Train NS 8922 Utrecht Centraal – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 08:34 No data
- Utrecht Centraal08:05
- Utrecht Leidsche Rijn08:09
- Utrecht Terwijde08:11
- Vleuten08:15
- Woerden08:21
- Bodegraven08:30
Next service: tomorrow 08:05 from Utrecht Centraal · Fri 6 Nov
Last 30 days
Arrival delay at Bodegraven, 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 7 Oct Max en route +5 min · last fix heading to Leiden Lammenschans +4 min
Distribution · 90 days
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 7
- 3–10 min 13% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=2
- 50% W n=2
- 100% T n=1
- 100% F n=2
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 8 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 |
|---|---|---|---|
| 08:05 | on time | on time | |
| 08:09 | — | — | |
| 08:11 | — | — | |
| 08:15 | — | — | |
| 08:21 / 08:22 | — | — | |
| 08:30 | — | — |
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 |
|---|---|---|---|
| Thu 5 Nov | Woerden 08:34 | No data | — |
| Wed 4 Nov | Woerden 08:34Partial coverage | 0 min | — |
| Tue 3 Nov | Woerden 08:34 | No data | — |
| Mon 2 Nov | Woerden 08:34 | No data | — |
| Fri 30 Oct | Woerden 08:36Partial coverage | 0 min | — |
| Thu 29 Oct | Woerden 08:36 | No data | — |
| Wed 28 Oct | Woerden 08:36 | No data | — |
| Tue 27 Oct | Woerden 08:36Partial coverage | 0 min | — |
| Mon 26 Oct | Woerden 08:36 | No data | — |
| Fri 23 Oct | Woerden 08:36 | No data | — |
| Thu 22 Oct | Woerden 08:36 | No data | — |
| Wed 21 Oct | Woerden 08:36 | No data | — |
| Tue 20 Oct | Woerden 08:36 | No data | — |
| Fri 16 Oct | Woerden 08:36 | No data | — |
| Thu 15 Oct | Woerden 08:36 | No data | — |
| Wed 14 Oct | Woerden 08:36 | No data | — |
| Tue 13 Oct | Woerden 08:36 | No data | — |
| Mon 12 Oct | Woerden 08:36Partial coverage | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 09:02 | 0 min | — |
| Thu 8 Oct | Leiden Lammenschans 09:02 | +1 min | — |
| Wed 7 Oct | Leiden Lammenschans 09:06 | +4 min | +5 min |
| Tue 6 Oct | Leiden Lammenschans 09:04 | +2 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 09:02 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 09:03 | No data | — |
| Thu 1 Oct | Leiden Lammenschans 09:03 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 09:03 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 09:03 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 09:03 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 09:02 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 09:03 | No data | — |