Train NS 8861 Bodegraven – 's-Hertogenbosch
✓ Today’s run finished
Today, last fix heading to Zaltbommel at 18:02 0 min
- Bodegraven16:46
- Utrecht Centraal17:06
- Utrecht Vaartsche Rijn17:12
- Houten17:18
- Culemborg17:28
- Zaltbommel17:48
- 's-Hertogenbosch17:57
Next service: tomorrow 16:46 from Bodegraven · Sun 8 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
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=3
- 100% T n=1
- 100% W n=2
- 100% T n=1
- — F n=0
- 100% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 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 |
|---|---|---|---|
| 16:46 | on time | on time | |
| 16:53 / 16:55 | ≈ on time | ≈ on time | |
| 17:06 / 17:10 | ≈ on time | ≈ +1 min | |
| 17:12 | ≈ on time | ≈ +1 min | |
| 17:15 | ≈ on time | ≈ +1 min | |
| 17:18 / 17:19 | ≈ on time | ≈ +1 min | |
| 17:22 | ≈ on time | ≈ +1 min | |
| 17:28 | ≈ on time | ≈ +1 min | |
| 17:36 / 17:42 | ≈ on time | ≈ +1 min | |
| 17:48 | ≈ on time | ≈ +1 min | |
| 17:57 | on time | +1 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 |
|---|---|---|---|
| Sat 7 Nov | Zaltbommel 18:02Partial coverage | 0 min | — |
| Thu 5 Nov | Zaltbommel 18:02 | No data | — |
| Wed 4 Nov | Zaltbommel 18:02 | No data | — |
| Tue 3 Nov | Zaltbommel 18:02 | No data | — |
| Mon 2 Nov | Zaltbommel 18:02 | No data | — |
| Thu 29 Oct | Zaltbommel 18:02 | No data | — |
| Wed 28 Oct | Zaltbommel 18:04 | No data | — |
| Tue 27 Oct | Zaltbommel 18:29 | No data | — |
| Mon 26 Oct | Zaltbommel 18:02 | +1 min | +1 min |
| Thu 22 Oct | Zaltbommel 18:02 | No data | — |
| Wed 21 Oct | Zaltbommel 18:02 | 0 min | — |
| Tue 20 Oct | Zaltbommel 18:02 | No data | — |
| Mon 19 Oct | Zaltbommel 18:02 | 0 min | — |
| Thu 15 Oct | Zaltbommel 18:02 | No data | — |
| Wed 14 Oct | Zaltbommel 18:11 | No data | — |
| Tue 13 Oct | Zaltbommel 18:02 | No data | — |
| Mon 12 Oct | Zaltbommel 18:02 | 0 min | — |
| Thu 8 Oct | Culemborg 18:00 | +1 min | +1 min |
| Wed 7 Oct | Zaltbommel 18:02 | 0 min | — |
| Tue 6 Oct | Zaltbommel 18:02 | 0 min | — |
| Thu 1 Oct | Zaltbommel 18:02 | No data | — |
| Wed 30 Sept | Zaltbommel 18:02 | No data | — |
| Tue 29 Sept | Zaltbommel 18:02 | No data | — |
| Mon 28 Sept | Zaltbommel 18:02 | No data | — |
| Thu 24 Sept | Zaltbommel 18:03 | No data | — |
| Wed 23 Sept | Zaltbommel 18:02 | No data | — |
| Tue 22 Sept | Zaltbommel 18:02 | No data | — |
| Mon 21 Sept | Zaltbommel 18:02 | No data | — |
| Thu 17 Sept | Zaltbommel 18:02 | No data | — |
| Wed 16 Sept | Zaltbommel 18:02 | No data | — |