Train NS 6730 's-Hertogenbosch – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 10:18 0 min
- 's-Hertogenbosch09:03
- Geldermalsen09:18
- Culemborg09:29
- Houten09:39
- Utrecht Vaartsche Rijn09:46
- Woerden10:03
- Bodegraven10:12
Next service: tomorrow 09:03 from 's-Hertogenbosch · Sun 25 Oct
Next departure 09:03 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 8 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min
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
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 7
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=2
- 100% S n=3
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
| Stop | Sched. |
|---|---|
| 09:03 | |
| 09:11 | |
| 09:18 / 09:24 | |
| 09:29 | |
| 09:35 / 09:36 | |
| 09:39 | |
| 09:43 | |
| 09:46 | |
| 09:49 / 09:53 | |
| 10:03 / 10:04 | |
| 10:12 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 24 Oct | Woerden 10:18Partial coverage | 0 min | — |
| Fri 23 Oct | Woerden 10:28 | 0 min | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 10:07 | 0 min | — |
| Sat 17 Oct | Woerden 10:21 | 0 min | — |
| Fri 16 Oct | Woerden 10:21 | No data | — |
| Sun 11 Oct | Leiden Lammenschans 10:47 | +1 min | — |
| Sat 10 Oct | Leiden Lammenschans 10:48 | 0 min | +4 min |
| Fri 9 Oct | Leiden Lammenschans 10:47 | +1 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 10:48 | No data | — |
| Sun 4 Oct | Leiden Lammenschans 10:47 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 10:48 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 10:47 | No data | — |
| Sun 27 Sept | Leiden Lammenschans 10:47 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 10:48 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 10:48 | No data | — |
| Sun 20 Sept | Leiden Lammenschans 10:48 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 10:47 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 10:48 | No data | — |
| Sun 13 Sept | Leiden Lammenschans 10:47 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 10:47 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 11:05 | No data | — |
| Sun 6 Sept | Leiden Lammenschans 10:47 | No data | — |
| Sat 5 Sept | Leiden Lammenschans 10:47 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 10:47 | No data | — |
| Sun 30 Aug | Leiden Lammenschans 10:47 | No data | — |
| Sat 29 Aug | Leiden Lammenschans 10:47 | No data | — |
| Fri 28 Aug | Leiden Lammenschans 10:47 | No data | — |
| Sun 23 Aug | Utrecht Vaartsche Rijn 10:22 | No data | — |
| Sat 22 Aug | Utrecht Vaartsche Rijn 10:33 | No data | — |
| Fri 21 Aug | Utrecht Vaartsche Rijn 10:07 | No data | — |