Train NS 8860 's-Hertogenbosch – Bodegraven
Running now · updated 18:07
Heading to Bodegraven 0 min
Estimated arrival at Bodegraven 18:15 · 2 km/h
- 's-Hertogenbosch17:03
- Geldermalsen17:18
- Culemborg17:29
- Houten17:39
- Utrecht Vaartsche Rijn17:46
- Utrecht Centraal17:49
- Bodegraven18:15
Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 11 runs arrived on time.
Last 30 days
Arrival delay at Bodegraven, 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
14 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 14
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=3
- 100% W n=2
- 100% T n=4
- — 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, 14 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 | Today |
|---|---|---|---|---|
| 17:03 | on time | on time | ||
| 17:11 | ≈ on time | ≈ on time | ||
| 17:18 / 17:24 | ≈ on time | ≈ on time | ||
| 17:29 | ≈ on time | ≈ on time | ||
| 17:35 / 17:36 | ≈ on time | ≈ on time | ||
| 17:39 | ≈ on time | ≈ on time | ||
| 17:43 | ≈ on time | ≈ on time | ||
| 17:46 | ≈ on time | ≈ on time | ||
| 17:49 / 17:55 | ≈ on time | ≈ on time | ||
| 18:05 / 18:07 | ≈ on time | ≈ on time | ||
| 18:15 | 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 |
|---|---|---|---|
| Sat 7 Nov | Woerden 18:04Partial coverage | 0 min | — |
| Thu 5 Nov | Woerden 18:19 | 0 min | — |
| Wed 4 Nov | Woerden 18:19 | No data | — |
| Tue 3 Nov | Woerden 18:19 | No data | — |
| Mon 2 Nov | Woerden 18:19 | 0 min | — |
| Thu 29 Oct | Utrecht Leidsche Rijn 18:17 | 0 min | — |
| Wed 28 Oct | Woerden 18:43 | No data | — |
| Tue 27 Oct | Utrecht Leidsche Rijn 18:17 | 0 min | — |
| Mon 26 Oct | Woerden 18:21 | 0 min | — |
| Thu 22 Oct | Woerden 18:21 | No data | — |
| Wed 21 Oct | Woerden 18:21 | No data | — |
| Tue 20 Oct | Woerden 18:21 | 0 min | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 18:05 | 0 min | — |
| Thu 15 Oct | Woerden 18:29 | 0 min | — |
| Wed 14 Oct | Woerden 18:21 | 0 min | — |
| Tue 13 Oct | Woerden 18:21 | No data | — |
| Mon 12 Oct | Woerden 18:21 | 0 min | — |
| Thu 8 Oct | Utrecht Leidsche Rijn 18:41 | +1 min | — |
| Wed 7 Oct | Utrecht Vaartsche Rijn 18:44 | 0 min | +7 min |
| Tue 6 Oct | Utrecht Leidsche Rijn 18:38 | 0 min | — |
| Thu 1 Oct | Utrecht Leidsche Rijn 18:12 | No data | — |
| Wed 30 Sept | Woerden 18:18 | No data | — |
| Tue 29 Sept | Woerden 18:21 | No data | — |
| Mon 28 Sept | Utrecht Leidsche Rijn 18:12 | No data | — |
| Thu 24 Sept | Utrecht Centraal 18:09 | No data | — |
| Wed 23 Sept | Woerden 18:21 | No data | — |
| Tue 22 Sept | Utrecht Leidsche Rijn 18:08 | No data | — |
| Mon 21 Sept | Woerden 18:21 | No data | — |
| Thu 17 Sept | Woerden 18:21 | No data | — |
| Wed 16 Sept | Utrecht Leidsche Rijn 18:12 | No data | — |