Train NS 6714 Utrecht Centraal – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 06:19 0 min
- Utrecht Centraal05:56
- Woerden06:06
- Bodegraven06:15
Next service: Friday 05:56 from Utrecht Centraal · Fri 20 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
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 5
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 5 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 |
|---|---|---|---|
| 05:56 | on time | on time | |
| 06:06 / 06:07 | — | — | |
| 06:15 | — | — |
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 06:19Partial coverage | 0 min | — |
| Fri 6 Nov | Woerden 06:19 | No data | — |
| Fri 30 Oct | Woerden 06:21Partial coverage | 0 min | +1 min |
| Fri 23 Oct | Woerden 06:21Partial coverage | 0 min | +1 min |
| Fri 16 Oct | Woerden 06:21Partial coverage | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 06:47 | +1 min | — |
| Mon 5 Oct | Leiden Lammenschans 06:49 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 06:48 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 06:48 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 06:47 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 06:49 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 06:47 | No data | — |
| Fri 28 Aug | Leiden Lammenschans 06:47 | No data | — |