Train NS 8832 's-Hertogenbosch – Bodegraven
It does not run today
Last recorded run: Thursday 5 November No data
Next service: tomorrow 10:03 from 's-Hertogenbosch · Sat 7 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
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 8
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 100% W n=3
- 100% T n=1
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 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 |
|---|---|---|---|
| 10:03 | on time | on time | |
| 10:11 | — | — | |
| 10:18 / 10:24 | — | — | |
| 10:29 | — | — | |
| 10:35 / 10:36 | — | — | |
| 10:39 | — | — | |
| 10:43 | — | — | |
| 10:46 | — | — | |
| 10:49 / 10:54 | — | — | |
| 10:58 | — | — | |
| 11:06 / 11:07 | — | — | |
| 11: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 |
|---|---|---|---|
| Thu 5 Nov | Woerden 11:19 | No data | — |
| Wed 4 Nov | Woerden 11:19Partial coverage | 0 min | — |
| Tue 3 Nov | Woerden 11:19 | No data | — |
| Mon 2 Nov | Woerden 11:24 | No data | — |
| Thu 29 Oct | Woerden 11:24 | No data | — |
| Wed 28 Oct | Woerden 11:22 | No data | — |
| Tue 27 Oct | Woerden 11:23Partial coverage | 0 min | — |
| Mon 26 Oct | Woerden 11:21 | No data | — |
| Thu 22 Oct | Woerden 11:30 | No data | — |
| Wed 21 Oct | Woerden 11:21 | No data | — |
| Tue 20 Oct | Woerden 11:21 | No data | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 11:05 | 0 min | — |
| Thu 15 Oct | Woerden 11:21 | No data | — |
| Wed 14 Oct | Woerden 11:22Partial coverage | 0 min | — |
| Tue 13 Oct | Woerden 11:22 | No data | — |
| Mon 12 Oct | Woerden 11:21Partial coverage | 0 min | — |
| Thu 8 Oct | Leiden Lammenschans 11:49 | +1 min | +3 min |
| Wed 7 Oct | Houten Castellum 12:01 | 0 min | — |
| Tue 6 Oct | Leiden Lammenschans 11:47 | 0 min | — |
| Thu 1 Oct | Leiden Lammenschans 11:50 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 11:48 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 11:47 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 11:48 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 11:47 | No data | — |
| Wed 23 Sept | Leiden Lammenschans 11:49 | No data | — |
| Tue 22 Sept | Leiden Lammenschans 11:50 | No data | — |
| Mon 21 Sept | Leiden Lammenschans 11:47 | No data | — |
| Thu 17 Sept | Leiden Lammenschans 11:47 | No data | — |
| Wed 16 Sept | Leiden Lammenschans 11:56 | No data | — |
| Tue 15 Sept | Leiden Lammenschans 11:47 | No data | — |