Train NS 8830 's-Hertogenbosch – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 10:49 0 min
- 's-Hertogenbosch09:33
- Geldermalsen09:48
- Houten Castellum10:05
- Utrecht Lunetten10:13
- Utrecht Vaartsche Rijn10:16
- Woerden10:36
- Bodegraven10:45
Next service: Monday 09:33 from 's-Hertogenbosch · Mon 16 Nov
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
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 16
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=5
- 100% W n=3
- 100% T n=4
- — 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, 16 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 |
|---|---|---|---|
| 09:33 | on time | on time | |
| 09:41 | ≈ on time | ≈ on time | |
| 09:48 / 09:54 | ≈ on time | ≈ on time | |
| 09:59 | ≈ on time | ≈ on time | |
| 10:05 / 10:06 | ≈ on time | ≈ on time | |
| 10:09 | ≈ on time | ≈ on time | |
| 10:13 | ≈ on time | ≈ on time | |
| 10:16 | ≈ on time | ≈ on time | |
| 10:19 / 10:24 | ≈ on time | ≈ on time | |
| 10:28 | ≈ on time | ≈ +1 min | |
| 10:36 / 10:37 | ≈ on time | ≈ +1 min | |
| 10:45 | 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 |
|---|---|---|---|
| Thu 12 Nov | Woerden 10:49Partial coverage | 0 min | — |
| Wed 11 Nov | Woerden 10:54Partial coverage | 0 min | — |
| Tue 10 Nov | Woerden 10:49Partial coverage | 0 min | +2 min |
| Mon 9 Nov | Woerden 10:49Partial coverage | 0 min | — |
| Sun 8 Nov | Woerden 10:49 | 0 min | — |
| Sat 7 Nov | Woerden 10:49 | 0 min | — |
| Thu 5 Nov | Woerden 10:49 | No data | — |
| Wed 4 Nov | Woerden 10:49Partial coverage | 0 min | — |
| Tue 3 Nov | Woerden 10:52 | No data | — |
| Mon 2 Nov | Woerden 10:49 | No data | — |
| Thu 29 Oct | Woerden 10:52Partial coverage | 0 min | — |
| Wed 28 Oct | Woerden 10:51 | No data | — |
| Tue 27 Oct | Woerden 10:51Partial coverage | 0 min | — |
| Mon 26 Oct | Woerden 10:51 | No data | — |
| Thu 22 Oct | Woerden 11:21 | No data | — |
| Wed 21 Oct | Woerden 10:51 | No data | — |
| Tue 20 Oct | Woerden 10:51Partial coverage | 0 min | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 10:36 | 0 min | — |
| Thu 15 Oct | Woerden 10:51Partial coverage | 0 min | — |
| Wed 14 Oct | Woerden 10:51 | No data | — |
| Tue 13 Oct | Woerden 10:51Partial coverage | 0 min | — |
| Mon 12 Oct | Woerden 10:51 | No data | — |
| Thu 8 Oct | Utrecht Vaartsche Rijn 11:33 | 0 min | +12 min |
| Wed 7 Oct | Woerden 12:01 | 0 min | — |
| Tue 6 Oct | Leiden Lammenschans 11:19 | +2 min | +2 min |
| Thu 1 Oct | Leiden Lammenschans 11:17 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 11:24 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 11:17 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 11:18 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 11:17 | No data | — |