Train NS 8846 's-Hertogenbosch – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 14:50 0 min
- 's-Hertogenbosch13:33
- Geldermalsen13:48
- Culemborg13:59
- Houten14:09
- Utrecht Vaartsche Rijn14:16
- Woerden14:35
- Bodegraven14:45
Next service: tomorrow 13:33 from 's-Hertogenbosch · Sun 8 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
Worst days
- Wed 4 Nov Max en route +15 min · last fix heading to Woerden +13 min
Distribution · 90 days
9 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 8
- 3–10 min 0% · 0
- 10–30 min 11% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=3
- 50% W n=2
- 100% T n=2
- — 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, 9 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 |
|---|---|---|---|
| 13:33 | on time | on time | |
| 13:41 | ≈ on time | ≈ +1 min | |
| 13:48 / 13:54 | ≈ on time | ≈ +1 min | |
| 13:59 | ≈ on time | ≈ +2 min | |
| 14:05 / 14:06 | ≈ on time | ≈ +2 min | |
| 14:09 | ≈ on time | ≈ +3 min | |
| 14:13 | ≈ on time | ≈ +3 min | |
| 14:16 | ≈ on time | ≈ +3 min | |
| 14:19 / 14:25 | ≈ on time | ≈ +3 min | |
| 14:35 / 14:37 | ≈ on time | ≈ +4 min | |
| 14:45 | on time | +5 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 | Woerden 14:50Partial coverage | 0 min | — |
| Thu 5 Nov | Woerden 14:49 | No data | — |
| Wed 4 Nov | Woerden 15:04 | +13 min | +15 min |
| Tue 3 Nov | Woerden 14:49 | No data | — |
| Mon 2 Nov | Woerden 14:49 | No data | — |
| Thu 29 Oct | Woerden 14:52 | 0 min | — |
| Wed 28 Oct | Woerden 14:51 | No data | — |
| Tue 27 Oct | Woerden 14:51 | No data | — |
| Mon 26 Oct | Woerden 14:51 | No data | — |
| Thu 22 Oct | Woerden 14:51 | No data | — |
| Wed 21 Oct | Woerden 14:51 | No data | — |
| Tue 20 Oct | Woerden 14:52 | 0 min | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 14:36 | 0 min | — |
| Thu 15 Oct | Woerden 14:51 | No data | — |
| Wed 14 Oct | Woerden 14:51 | No data | — |
| Tue 13 Oct | Woerden 14:52 | 0 min | — |
| Mon 12 Oct | Woerden 14:52 | No data | — |
| Thu 8 Oct | Leiden Lammenschans 15:17 | 0 min | — |
| Wed 7 Oct | Leiden Lammenschans 15:18 | +2 min | +2 min |
| Tue 6 Oct | Leiden Lammenschans 15:17 | 0 min | — |
| Thu 1 Oct | Leiden Lammenschans 15:17 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 15:17 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 15:18 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 15:17 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 15:17 | No data | — |
| Wed 23 Sept | Leiden Lammenschans 15:17 | No data | — |
| Tue 22 Sept | Leiden Lammenschans 15:18 | No data | — |
| Mon 21 Sept | Leiden Lammenschans 15:17 | No data | — |
| Thu 17 Sept | Leiden Lammenschans 15:17 | No data | — |
| Wed 16 Sept | Leiden Lammenschans 15:18 | No data | — |