Train NS 8829 Bodegraven – 's-Hertogenbosch
✓ Today’s run finished
Today, last fix heading to Zaltbommel at 10:04 +2 min
- Bodegraven08:46
- Utrecht Leidsche Rijn09:02
- Utrecht Vaartsche Rijn09:12
- Houten09:18
- Houten Castellum09:22
- Zaltbommel09:48
- 's-Hertogenbosch09:57
Next service: tomorrow 08:46 from Bodegraven · Tue 17 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
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 17
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=2
- 100% W n=5
- 100% T n=2
- — 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 |
|---|---|---|---|
| 08:46 | on time | on time | |
| 08:53 / 08:54 | ≈ on time | ≈ on time | |
| 09:02 | ≈ on time | ≈ on time | |
| 09:06 / 09:10 | ≈ on time | ≈ on time | |
| 09:12 | ≈ on time | ≈ on time | |
| 09:15 | ≈ on time | ≈ on time | |
| 09:18 / 09:19 | ≈ on time | ≈ on time | |
| 09:22 | ≈ on time | ≈ on time | |
| 09:28 | ≈ on time | ≈ on time | |
| 09:36 / 09:42 | ≈ on time | ≈ on time | |
| 09:48 | ≈ on time | ≈ on time | |
| 09: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 |
|---|---|---|---|
| Mon 16 Nov | Zaltbommel 10:04Partial coverage | +2 min | +2 min |
| Thu 12 Nov | Zaltbommel 10:02Partial coverage | 0 min | — |
| Wed 11 Nov | Zaltbommel 10:03Partial coverage | 0 min | — |
| Tue 10 Nov | Zaltbommel 10:02Partial coverage | 0 min | — |
| Mon 9 Nov | Zaltbommel 10:03Partial coverage | 0 min | — |
| Sun 8 Nov | Zaltbommel 10:03 | +1 min | +1 min |
| Sat 7 Nov | Zaltbommel 10:02 | 0 min | — |
| Thu 5 Nov | Zaltbommel 10:04 | No data | — |
| Wed 4 Nov | Zaltbommel 10:02Partial coverage | 0 min | — |
| Tue 3 Nov | Zaltbommel 10:02 | No data | — |
| Mon 2 Nov | Zaltbommel 10:02Partial coverage | 0 min | — |
| Thu 29 Oct | Zaltbommel 10:02 | No data | — |
| Wed 28 Oct | Zaltbommel 10:02Partial coverage | 0 min | — |
| Tue 27 Oct | Zaltbommel 10:02 | No data | — |
| Mon 26 Oct | Zaltbommel 10:02Partial coverage | 0 min | — |
| Thu 22 Oct | Zaltbommel 10:02 | No data | — |
| Wed 21 Oct | Zaltbommel 10:02 | No data | — |
| Tue 20 Oct | Zaltbommel 10:02 | No data | — |
| Mon 19 Oct | Zaltbommel 10:04 | 0 min | — |
| Thu 15 Oct | Culemborg 10:58 | No data | — |
| Wed 14 Oct | Zaltbommel 10:02Partial coverage | 0 min | — |
| Tue 13 Oct | Zaltbommel 10:03 | No data | — |
| Mon 12 Oct | Zaltbommel 10:03Partial coverage | 0 min | — |
| Thu 8 Oct | Zaltbommel 10:02 | 0 min | — |
| Wed 7 Oct | Zaltbommel 10:02 | 0 min | — |
| Tue 6 Oct | Zaltbommel 10:02 | 0 min | — |
| Thu 1 Oct | Zaltbommel 10:02 | No data | — |
| Wed 30 Sept | Zaltbommel 10:03 | No data | — |
| Tue 29 Sept | Zaltbommel 10:02 | No data | — |
| Mon 28 Sept | Zaltbommel 10:02 | No data | — |