Train NS 8929 Bodegraven – Utrecht Centraal
It does not run today
Last recorded run: Friday 13 November 0 min
Next service: Monday 08:31 from Bodegraven · Mon 16 Nov
Last 30 days
Arrival delay at Utrecht Centraal, 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
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 16
- 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=4
- 100% W n=6
- 100% T n=3
- 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, 16 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:31 | on time | on time | |
| 08:39 / 08:44 | ≈ on time | ≈ on time | |
| 08:50 | ≈ on time | ≈ on time | |
| 08:53 | ≈ on time | ≈ on time | |
| 08:56 | ≈ on time | ≈ on time | |
| 09:01 | on time | on time |
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 |
|---|---|---|---|
| Fri 13 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | 0 min | — |
| Thu 12 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | +1 min | +1 min |
| Wed 11 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | 0 min | — |
| Tue 10 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | 0 min | — |
| Mon 9 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | 0 min | — |
| Fri 6 Nov | Utrecht Leidsche Rijn 09:19 | No data | — |
| Thu 5 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | 0 min | — |
| Wed 4 Nov | Utrecht Leidsche Rijn 09:09Partial coverage | +1 min | — |
| Tue 3 Nov | Utrecht Leidsche Rijn 09:09 | No data | — |
| Mon 2 Nov | Utrecht Leidsche Rijn 09:09 | No data | — |
| Fri 30 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Thu 29 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Wed 28 Oct | Utrecht Leidsche Rijn 09:11Partial coverage | 0 min | — |
| Tue 27 Oct | Utrecht Leidsche Rijn 09:10Partial coverage | 0 min | — |
| Mon 26 Oct | Utrecht Leidsche Rijn 09:11 | No data | — |
| Fri 23 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Thu 22 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Wed 21 Oct | Utrecht Leidsche Rijn 09:18Partial coverage | 0 min | — |
| Tue 20 Oct | Utrecht Leidsche Rijn 09:10Partial coverage | 0 min | — |
| Fri 16 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Thu 15 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Wed 14 Oct | Utrecht Leidsche Rijn 09:10 | 0 min | — |
| Tue 13 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Mon 12 Oct | Utrecht Leidsche Rijn 09:11 | No data | — |
| Fri 9 Oct | Utrecht Leidsche Rijn 09:10 | 0 min | — |
| Thu 8 Oct | Utrecht Leidsche Rijn 09:10 | 0 min | — |
| Wed 7 Oct | Utrecht Leidsche Rijn 09:10 | 0 min | — |
| Tue 6 Oct | Utrecht Leidsche Rijn 09:10 | 0 min | — |
| Mon 5 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |
| Fri 2 Oct | Utrecht Leidsche Rijn 09:10 | No data | — |