Train NS 8862 's-Hertogenbosch – Bodegraven
It has not run yet today
Last recorded run: Monday 16 November 0 min
Next service: today 17:33 from 's-Hertogenbosch · Tue 17 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
- Wed 7 Oct Max en route +6 min · last fix heading to Houten +6 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 17
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 67% W n=3
- 100% T n=4
- — F n=0
- 100% S n=1
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 17:33 | on time | on time | |
| 17:41 | ≈ on time | ≈ on time | |
| 17:48 / 17:54 | ≈ on time | ≈ +1 min | |
| 17:59 | ≈ on time | ≈ +1 min | |
| 18:05 / 18:06 | ≈ on time | ≈ +1 min | |
| 18:09 | ≈ on time | ≈ +2 min | |
| 18:13 | ≈ on time | ≈ +2 min | |
| 18:16 | ≈ on time | ≈ +2 min | |
| 18:19 / 18:24 | ≈ on time | ≈ +2 min | |
| 18:28 | ≈ on time | ≈ +2 min | |
| 18:36 / 18:37 | ≈ on time | ≈ +3 min | |
| 18:45 | on time | +3 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 |
|---|---|---|---|
| Mon 16 Nov | Utrecht Centraal 18:45Partial coverage | 0 min | — |
| Thu 12 Nov | Utrecht Vaartsche Rijn 18:48Partial coverage | +1 min | +1 min |
| Wed 11 Nov | Utrecht Lunetten 18:44Partial coverage | 0 min | — |
| Tue 10 Nov | Utrecht Vaartsche Rijn 18:47Partial coverage | +1 min | — |
| Mon 9 Nov | Utrecht Lunetten 18:47Partial coverage | 0 min | — |
| Sun 8 Nov | Woerden 18:52 | 0 min | +4 min |
| Sat 7 Nov | Woerden 18:49 | 0 min | — |
| Thu 5 Nov | Utrecht Lunetten 18:44 | No data | — |
| Wed 4 Nov | Utrecht Lunetten 18:47 | No data | — |
| Tue 3 Nov | Houten 18:49 | No data | — |
| Mon 2 Nov | Houten 18:23 | No data | — |
| Thu 29 Oct | Culemborg 18:47Partial coverage | +1 min | — |
| Wed 28 Oct | Utrecht Lunetten 18:46Partial coverage | 0 min | — |
| Tue 27 Oct | Culemborg 18:47 | No data | — |
| Mon 26 Oct | Houten 18:23Partial coverage | 0 min | — |
| Thu 22 Oct | Woerden 18:51Partial coverage | 0 min | — |
| Wed 21 Oct | Woerden 18:51 | No data | — |
| Tue 20 Oct | Woerden 18:50Partial coverage | 0 min | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 18:35 | 0 min | — |
| Thu 15 Oct | Utrecht Leidsche Rijn 18:42 | No data | — |
| Wed 14 Oct | Woerden 18:51 | No data | — |
| Tue 13 Oct | Woerden 18:50Partial coverage | 0 min | — |
| Mon 12 Oct | Utrecht Centraal 19:11Partial coverage | 0 min | — |
| Thu 8 Oct | Culemborg 19:09 | 0 min | — |
| Wed 7 Oct | Houten 19:20 | +6 min | +6 min |
| Tue 6 Oct | Culemborg 18:13 | 0 min | — |
| Thu 1 Oct | Houten Castellum 18:20 | No data | — |
| Wed 30 Sept | Houten 18:18 | No data | — |
| Tue 29 Sept | Houten Castellum 18:20 | No data | — |
| Mon 28 Sept | Culemborg 18:13 | No data | — |