Train NS 8859 Bodegraven – 's-Hertogenbosch
✓ Today’s run finished
Today, last fix heading to Zaltbommel at 17:32 0 min
- Bodegraven16:16
- Utrecht Centraal16:36
- Utrecht Vaartsche Rijn16:42
- Houten16:48
- Culemborg16:58
- Zaltbommel17:18
- 's-Hertogenbosch17:27
Next service: tomorrow 16:16 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
Worst days
- Tue 6 Oct Max en route +20 min · last fix heading to Zaltbommel +20 min
- Thu 8 Oct Max en route +3 min · last fix heading to Zaltbommel +3 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 8
- 3–10 min 10% · 1
- 10–30 min 10% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 67% T n=3
- 100% W n=1
- 67% T n=3
- — 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, 10 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:16 | on time | on time | |
| 16:23 / 16:25 | ≈ on time | ≈ +1 min | |
| 16:36 / 16:40 | ≈ on time | ≈ +2 min | |
| 16:42 | ≈ on time | ≈ +2 min | |
| 16:45 | ≈ on time | ≈ +3 min | |
| 16:48 / 16:49 | ≈ on time | ≈ +3 min | |
| 16:52 | ≈ on time | ≈ +3 min | |
| 16:58 | ≈ on time | ≈ +4 min | |
| 17:06 / 17:12 | ≈ on time | ≈ +4 min | |
| 17:18 | ≈ on time | ≈ +6 min | |
| 17:27 | on time | +6 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 17:32Partial coverage | 0 min | — |
| Thu 5 Nov | Zaltbommel 17:32 | No data | — |
| Wed 4 Nov | Zaltbommel 17:32 | No data | — |
| Tue 3 Nov | Zaltbommel 17:32 | No data | — |
| Mon 2 Nov | Zaltbommel 17:32 | No data | — |
| Thu 29 Oct | Zaltbommel 17:34 | 0 min | — |
| Wed 28 Oct | Zaltbommel 17:33 | No data | — |
| Tue 27 Oct | Geldermalsen 17:43 | No data | — |
| Mon 26 Oct | Zaltbommel 17:32 | No data | — |
| Thu 22 Oct | Zaltbommel 17:32 | 0 min | — |
| Wed 21 Oct | Zaltbommel 17:32 | No data | — |
| Tue 20 Oct | Zaltbommel 17:33 | 0 min | — |
| Mon 19 Oct | Zaltbommel 17:33 | 0 min | — |
| Thu 15 Oct | Zaltbommel 17:32 | No data | — |
| Wed 14 Oct | Zaltbommel 17:32 | No data | — |
| Tue 13 Oct | Zaltbommel 17:32 | 0 min | — |
| Mon 12 Oct | Zaltbommel 17:37 | 0 min | — |
| Thu 8 Oct | Zaltbommel 17:33 | +3 min | +3 min |
| Wed 7 Oct | Utrecht Vaartsche Rijn 17:37 | 0 min | — |
| Tue 6 Oct | Zaltbommel 17:51 | +20 min | +20 min |
| Thu 1 Oct | Zaltbommel 17:32 | No data | — |
| Wed 30 Sept | Zaltbommel 17:32 | No data | — |
| Tue 29 Sept | Zaltbommel 17:32 | No data | — |
| Mon 28 Sept | Zaltbommel 17:32 | No data | — |
| Thu 24 Sept | Zaltbommel 17:29 | No data | — |
| Wed 23 Sept | Zaltbommel 17:32 | No data | — |
| Tue 22 Sept | Zaltbommel 17:32 | No data | — |
| Mon 21 Sept | Zaltbommel 17:32 | No data | — |
| Thu 17 Sept | Zaltbommel 17:32 | No data | — |
| Wed 16 Sept | Zaltbommel 17:32 | No data | — |