Train NS 6762 's-Hertogenbosch – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 18:21 0 min
- 's-Hertogenbosch17:03
- Geldermalsen17:18
- Culemborg17:29
- Houten17:39
- Utrecht Vaartsche Rijn17:46
- Woerden18:05
- Bodegraven18:14
Next service: tomorrow 17:03 from 's-Hertogenbosch · Sat 24 Oct
Next departure 17:03 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 7 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
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- 100% F n=2
- 100% S n=2
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
| Stop | Sched. |
|---|---|
| 17:03 | |
| 17:11 | |
| 17:18 / 17:24 | |
| 17:29 | |
| 17:35 / 17:36 | |
| 17:39 | |
| 17:43 | |
| 17:46 | |
| 17:49 / 17:56 | |
| 18:05 / 18:06 | |
| 18:14 |
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 |
|---|---|---|---|
| Fri 23 Oct | Woerden 18:21Partial coverage | 0 min | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 18:07 | 0 min | — |
| Sat 17 Oct | Woerden 18:21 | 0 min | — |
| Fri 16 Oct | Woerden 18:22 | No data | — |
| Sun 11 Oct | Leiden Lammenschans 18:47 | 0 min | — |
| Sat 10 Oct | Leiden Lammenschans 18:47 | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 18:46 | +1 min | +2 min |
| Mon 5 Oct | Woerden 18:40 | +1 min | +1 min |
| Sun 4 Oct | Leiden Lammenschans 18:47 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 18:48 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 18:46 | No data | — |
| Sun 27 Sept | Leiden Lammenschans 18:47 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 18:47 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 18:46 | No data | — |
| Sun 20 Sept | Leiden Lammenschans 18:47 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 18:59 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 18:46 | No data | — |
| Sun 13 Sept | Leiden Lammenschans 18:47 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 18:47 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 18:43 | No data | — |
| Sun 6 Sept | Leiden Lammenschans 19:01 | No data | — |
| Sat 5 Sept | Leiden Lammenschans 18:47 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 18:46 | No data | — |
| Sun 30 Aug | Leiden Lammenschans 18:47 | No data | — |
| Sat 29 Aug | Leiden Lammenschans 18:48 | No data | — |
| Fri 28 Aug | Leiden Lammenschans 18:46 | No data | — |
| Sun 23 Aug | Utrecht Vaartsche Rijn 18:22 | No data | — |
| Sat 22 Aug | Utrecht Vaartsche Rijn 18:22 | No data | — |
| Fri 21 Aug | Utrecht Vaartsche Rijn 18:07 | No data | — |
| Sun 16 Aug | Leiden Lammenschans 18:47 | No data | — |