Train NS 8865 Bodegraven – 's-Hertogenbosch
It has not run yet today
Last recorded run: Wednesday 11 November +2 min
Next service: today 17:46 from Bodegraven · Thu 12 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
- Wed 7 Oct Max en route +13 min · last fix heading to Utrecht Leidsche Rijn +12 min
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 16
- 3–10 min 0% · 0
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=3
- 75% W n=4
- 100% 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, 17 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:46 | on time | on time | |
| 17:53 / 17:54 | ≈ on time | ≈ on time | |
| 18:02 | ≈ on time | ≈ +1 min | |
| 18:06 / 18:10 | ≈ on time | ≈ +1 min | |
| 18:12 | ≈ on time | ≈ +1 min | |
| 18:15 | ≈ on time | ≈ +1 min | |
| 18:18 / 18:19 | ≈ on time | ≈ +1 min | |
| 18:22 | ≈ on time | ≈ +1 min | |
| 18:28 | ≈ on time | ≈ +2 min | |
| 18:36 / 18:44 | ≈ on time | ≈ +2 min | |
| 18:50 | ≈ on time | ≈ +2 min | |
| 18:59 | 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 |
|---|---|---|---|
| Wed 11 Nov | Utrecht Vaartsche Rijn 18:59Partial coverage | +2 min | +2 min |
| Tue 10 Nov | Houten 18:59Partial coverage | 0 min | — |
| Mon 9 Nov | Utrecht Vaartsche Rijn 18:59 | 0 min | — |
| Sun 8 Nov | Zaltbommel 19:02 | 0 min | — |
| Sat 7 Nov | Zaltbommel 19:03 | +1 min | +4 min |
| Thu 5 Nov | Utrecht Vaartsche Rijn 18:59 | 0 min | — |
| Wed 4 Nov | Utrecht Lunetten 18:59 | No data | — |
| Tue 3 Nov | Utrecht Vaartsche Rijn 18:59 | No data | — |
| Mon 2 Nov | Utrecht Centraal 18:59 | 0 min | — |
| Thu 29 Oct | Utrecht Leidsche Rijn 19:04 | +3 min | +3 min |
| Wed 28 Oct | Utrecht Vaartsche Rijn 19:00 | 0 min | — |
| Tue 27 Oct | Utrecht Leidsche Rijn 19:10 | No data | — |
| Mon 26 Oct | Utrecht Leidsche Rijn 18:59 | 0 min | — |
| Thu 22 Oct | Geldermalsen 19:00 | No data | — |
| Wed 21 Oct | Culemborg 19:01 | 0 min | — |
| Tue 20 Oct | Geldermalsen 19:00 | 0 min | — |
| Mon 19 Oct | Geldermalsen 18:56 | 0 min | — |
| Thu 15 Oct | Culemborg 19:00 | No data | — |
| Wed 14 Oct | Zaltbommel 19:03 | No data | — |
| Tue 13 Oct | Culemborg 19:00 | No data | — |
| Mon 12 Oct | Geldermalsen 18:59 | 0 min | — |
| Thu 8 Oct | Leiden Lammenschans 19:00 | 0 min | — |
| Wed 7 Oct | Utrecht Leidsche Rijn 19:19 | +12 min | +13 min |
| Tue 6 Oct | Utrecht Leidsche Rijn 19:00 | +2 min | +2 min |
| Thu 1 Oct | Utrecht Leidsche Rijn 18:16 | No data | — |
| Wed 30 Sept | Utrecht Leidsche Rijn 18:16 | No data | — |
| Tue 29 Sept | Utrecht Leidsche Rijn 18:16 | No data | — |
| Mon 28 Sept | Utrecht Leidsche Rijn 18:16 | No data | — |
| Thu 24 Sept | Woerden 18:09 | No data | — |
| Wed 23 Sept | Utrecht Centraal 18:24 | No data | — |