Train NS 8916 Utrecht Centraal – Bodegraven
It does not run today
Last recorded run: Friday 13 November +2 min
Next service: Monday 06:35 from Utrecht Centraal · Mon 16 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
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 27
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=6
- 100% W n=6
- 100% T n=6
- 100% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 06:35 | on time | on time | |
| 06:39 | ≈ on time | ≈ on time | |
| 06:41 | ≈ on time | ≈ on time | |
| 06:45 | ≈ on time | ≈ +1 min | |
| 06:51 / 06:52 | ≈ on time | ≈ +1 min | |
| 07:00 | 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 |
|---|---|---|---|
| Fri 13 Nov | Woerden 07:08Partial coverage | +2 min | +2 min |
| Thu 12 Nov | Woerden 07:04 | 0 min | — |
| Wed 11 Nov | Woerden 07:04 | 0 min | — |
| Tue 10 Nov | Vleuten 07:04 | 0 min | — |
| Mon 9 Nov | Woerden 07:04 | 0 min | — |
| Fri 6 Nov | Woerden 07:07 | No data | — |
| Thu 5 Nov | Woerden 07:04 | 0 min | — |
| Wed 4 Nov | Woerden 07:09 | +2 min | +4 min |
| Tue 3 Nov | Woerden 07:04 | 0 min | — |
| Mon 2 Nov | Woerden 07:04 | 0 min | — |
| Fri 30 Oct | Woerden 07:06Partial coverage | 0 min | — |
| Thu 29 Oct | Woerden 07:06 | 0 min | — |
| Wed 28 Oct | Woerden 07:06 | 0 min | — |
| Tue 27 Oct | Woerden 07:06 | 0 min | — |
| Mon 26 Oct | Woerden 07:06 | 0 min | — |
| Fri 23 Oct | Woerden 07:06Partial coverage | 0 min | — |
| Thu 22 Oct | Woerden 07:08 | +1 min | +4 min |
| Wed 21 Oct | Woerden 07:06 | 0 min | — |
| Tue 20 Oct | Woerden 07:06 | 0 min | — |
| Fri 16 Oct | Woerden 07:06Partial coverage | 0 min | — |
| Thu 15 Oct | Woerden 07:06 | 0 min | — |
| Wed 14 Oct | Woerden 07:06 | 0 min | — |
| Tue 13 Oct | Woerden 07:06 | 0 min | +1 min |
| Mon 12 Oct | Woerden 07:06 | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 07:33 | +1 min | +1 min |
| Thu 8 Oct | Leiden Lammenschans 07:33 | +1 min | +1 min |
| Wed 7 Oct | Leiden Lammenschans 07:33 | +2 min | +2 min |
| Tue 6 Oct | Leiden Lammenschans 07:32 | +1 min | — |
| Mon 5 Oct | Leiden Lammenschans 07:34 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 07:33 | No data | — |