Train NS 8950 Utrecht Centraal – Bodegraven
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 15:05 from Utrecht Centraal · Thu 5 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
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=4
- 100% T n=2
- 100% W n=3
- 100% T n=1
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 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 |
|---|---|---|---|
| 15:05 | on time | on time | |
| 15:09 | ≈ on time | ≈ on time | |
| 15:11 | ≈ on time | ≈ on time | |
| 15:15 | ≈ on time | ≈ +1 min | |
| 15:21 / 15:22 | ≈ on time | ≈ +1 min | |
| 15:30 | +1 min | +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 | Woerden 15:34Partial coverage | 0 min | +1 min |
| Tue 3 Nov | Woerden 15:34 | No data | — |
| Mon 2 Nov | Woerden 15:34Partial coverage | 0 min | — |
| Fri 30 Oct | Woerden 15:37Partial coverage | 0 min | — |
| Thu 29 Oct | Woerden 15:36 | No data | — |
| Wed 28 Oct | Woerden 15:36 | No data | — |
| Tue 27 Oct | Woerden 15:37 | No data | — |
| Mon 26 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Fri 23 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Thu 22 Oct | Woerden 15:36 | No data | — |
| Wed 21 Oct | Woerden 15:36 | No data | — |
| Tue 20 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Fri 16 Oct | Utrecht Centraal 15:45 | No data | — |
| Thu 15 Oct | Woerden 15:40 | No data | — |
| Wed 14 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Tue 13 Oct | Woerden 15:36 | No data | — |
| Mon 12 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 16:03 | +1 min | +2 min |
| Thu 8 Oct | Leiden Lammenschans 16:02 | 0 min | — |
| Wed 7 Oct | Leiden Lammenschans 16:02 | +1 min | +3 min |
| Tue 6 Oct | Leiden Lammenschans 16:04 | +2 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 16:02 | 0 min | — |
| Fri 2 Oct | Leiden Lammenschans 16:04 | No data | — |
| Thu 1 Oct | Leiden Lammenschans 16:03 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 16:02 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 16:02 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 16:03 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 16:02 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 16:02 | No data | — |
| Wed 23 Sept | Leiden Lammenschans 16:05 | No data | — |