Train NS 8867 Bodegraven – 's-Hertogenbosch
It does not run today
Last recorded run: Thursday 12 November 0 min
Next service: Monday 18:16 from Bodegraven · Mon 16 Nov
Last 30 days
Arrival delay at 's-Hertogenbosch, 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 7 Nov Max en route +8 min · last fix heading to Zaltbommel +4 min
- Thu 29 Oct Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 14
- 3–10 min 13% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=3
- 100% W n=3
- 67% T n=3
- — F n=0
- 0% 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, 16 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 |
|---|---|---|---|
| 18:16 | on time | on time | |
| 18:23 / 18:24 | ≈ on time | ≈ on time | |
| 18:32 | ≈ on time | ≈ +1 min | |
| 18:36 / 18:40 | ≈ on time | ≈ +1 min | |
| 18:42 | ≈ on time | ≈ +1 min | |
| 18:45 | ≈ on time | ≈ +1 min | |
| 18:48 / 18:49 | ≈ on time | ≈ +1 min | |
| 18:52 | ≈ on time | ≈ +2 min | |
| 18:58 | ≈ on time | ≈ +2 min | |
| 19:06 / 19:12 | ≈ on time | ≈ +2 min | |
| 19:18 | ≈ on time | ≈ +3 min | |
| 19:28 | 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 |
|---|---|---|---|
| Thu 12 Nov | Bodegraven 19:29Partial coverage | 0 min | — |
| Wed 11 Nov | — 19:29 | 0 min | — |
| Tue 10 Nov | Bodegraven 19:32Partial coverage | +1 min | — |
| Mon 9 Nov | — 19:29 | 0 min | — |
| Sun 8 Nov | Zaltbommel 19:34 | +3 min | +3 min |
| Sat 7 Nov | Zaltbommel 19:37 | +4 min | +8 min |
| Thu 5 Nov | — 19:29 | No data | — |
| Wed 4 Nov | — 19:29 | No data | — |
| Mon 2 Nov | — 19:38 | 0 min | — |
| Thu 29 Oct | — 19:29 | +3 min | +3 min |
| Wed 28 Oct | — 19:30 | 0 min | — |
| Tue 27 Oct | — 19:31 | No data | — |
| Mon 26 Oct | — 19:38 | 0 min | — |
| Thu 22 Oct | Utrecht Lunetten 19:30 | No data | — |
| Wed 21 Oct | Utrecht Centraal 19:30 | No data | — |
| Tue 20 Oct | Utrecht Lunetten 18:50Partial coverage | 0 min | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 19:29 | 0 min | — |
| Thu 15 Oct | Woerden 19:37 | No data | — |
| Wed 14 Oct | Zaltbommel 19:32 | No data | — |
| Tue 13 Oct | Utrecht Centraal 19:36 | No data | — |
| Mon 12 Oct | Utrecht Lunetten 19:31 | 0 min | — |
| Thu 8 Oct | Leiden Lammenschans 19:29 | 0 min | — |
| Wed 7 Oct | Alphen a/d Rijn 19:29 | 0 min | — |
| Tue 6 Oct | Leiden Lammenschans 19:29 | 0 min | — |
| Thu 1 Oct | Leiden Lammenschans 18:12 | No data | — |
| Wed 30 Sept | Alphen a/d Rijn 18:18 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 18:12 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 18:12 | No data | — |
| Thu 24 Sept | Leiden Centraal 18:08 | No data | — |
| Wed 23 Sept | Alphen a/d Rijn 18:23 | No data | — |