Train NS 8827 Bodegraven – 's-Hertogenbosch
It does not run today
Last recorded run: Thursday 12 November +3 min
Next service: Monday 08: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
- Thu 12 Nov Max en route +3 min · last fix heading to Zaltbommel +3 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=4
- 100% T n=5
- 100% W n=4
- 67% T n=3
- — 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 |
|---|---|---|---|
| 08:16 | on time | on time | |
| 08:23 / 08:24 | ≈ on time | ≈ on time | |
| 08:32 | ≈ on time | ≈ on time | |
| 08:36 / 08:40 | ≈ on time | ≈ on time | |
| 08:42 | ≈ on time | ≈ on time | |
| 08:45 | ≈ on time | ≈ on time | |
| 08:48 / 08:49 | ≈ on time | ≈ on time | |
| 08:52 | ≈ on time | ≈ on time | |
| 08:58 | ≈ on time | ≈ on time | |
| 09:06 / 09:12 | ≈ on time | ≈ on time | |
| 09:18 | ≈ on time | ≈ on time | |
| 09:27 | on time | on time |
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 | Zaltbommel 09:34Partial coverage | +3 min | +3 min |
| Wed 11 Nov | Zaltbommel 09:33 | 0 min | — |
| Tue 10 Nov | Zaltbommel 09:32Partial coverage | 0 min | — |
| Mon 9 Nov | Zaltbommel 09:34Partial coverage | +2 min | +2 min |
| Sun 8 Nov | Zaltbommel 09:32 | 0 min | — |
| Sat 7 Nov | Zaltbommel 09:32 | 0 min | — |
| Thu 5 Nov | Zaltbommel 09:32 | No data | — |
| Wed 4 Nov | Zaltbommel 09:32Partial coverage | 0 min | — |
| Tue 3 Nov | Zaltbommel 09:32 | No data | — |
| Mon 2 Nov | Zaltbommel 09:32Partial coverage | 0 min | — |
| Thu 29 Oct | Zaltbommel 09:32Partial coverage | 0 min | — |
| Wed 28 Oct | Zaltbommel 09:33 | 0 min | — |
| Tue 27 Oct | Zaltbommel 09:34Partial coverage | 0 min | — |
| Mon 26 Oct | Zaltbommel 09:32Partial coverage | 0 min | — |
| Thu 22 Oct | Zaltbommel 09:40 | No data | — |
| Wed 21 Oct | Zaltbommel 09:32 | No data | — |
| Tue 20 Oct | Zaltbommel 09:32Partial coverage | 0 min | — |
| Mon 19 Oct | Zaltbommel 09:32 | 0 min | — |
| Thu 15 Oct | Zaltbommel 10:58 | No data | — |
| Wed 14 Oct | Zaltbommel 09:32 | No data | — |
| Tue 13 Oct | Zaltbommel 09:32Partial coverage | 0 min | — |
| Mon 12 Oct | Zaltbommel 09:33 | No data | — |
| Thu 8 Oct | Zaltbommel 09:32 | 0 min | — |
| Wed 7 Oct | Zaltbommel 09:32 | 0 min | — |
| Tue 6 Oct | Zaltbommel 09:32 | 0 min | — |
| Thu 1 Oct | Zaltbommel 09:32 | No data | — |
| Wed 30 Sept | Zaltbommel 09:34 | No data | — |
| Tue 29 Sept | Zaltbommel 09:32 | No data | — |
| Mon 28 Sept | Zaltbommel 09:32 | No data | — |
| Thu 24 Sept | Zaltbommel 09:32 | No data | — |