Train NS 6716 Utrecht Centraal – Bodegraven
It does not run today
Last recorded run: Saturday 31 October 0 min
Next service: tomorrow 06:26 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
- Sat 17 Oct Max en route +13 min · last fix heading to Woerden +12 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 0% · 0
- 10–30 min 13% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=4
- 75% S n=4
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 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 |
|---|---|---|---|
| 06:26 | on time | on time | |
| 06:36 / 06:37 | ≈ on time | ≈ +1 min | |
| 06:45 | +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 |
|---|---|---|---|
| Sat 31 Oct | Woerden 06:52Partial coverage | 0 min | — |
| Fri 30 Oct | Woerden 06:52 | +1 min | +6 min |
| Sat 24 Oct | Woerden 06:51 | +1 min | — |
| Fri 23 Oct | Woerden 06:50 | 0 min | — |
| Sat 17 Oct | Woerden 07:10Partial coverage | +12 min | +13 min |
| Fri 16 Oct | Woerden 06:52 | +1 min | +1 min |
| Sat 10 Oct | Leiden Lammenschans 07:18 | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 07:19 | +2 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 07:19 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 07:18 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 07:20 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 07:19 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 07:17 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 07:18 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 07:19 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 07:17 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 07:17 | No data | — |
| Sat 5 Sept | Leiden Lammenschans 07:18 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 07:17 | No data | — |
| Sat 29 Aug | Leiden Lammenschans 07:17 | No data | — |
| Fri 28 Aug | Leiden Lammenschans 07:17 | No data | — |
| Fri 21 Aug | Utrecht Vaartsche Rijn 06:36 | No data | — |
| Sat 15 Aug | Leiden Lammenschans 07:19 | No data | — |
| Fri 14 Aug | Leiden Lammenschans 07:17 | No data | — |
| Sat 8 Aug | Bodegraven 07:01 | No data | — |