Train NS 6728 's-Hertogenbosch – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 09:48 0 min
- 's-Hertogenbosch08:33
- Geldermalsen08:48
- Culemborg08:59
- Houten09:09
- Utrecht Vaartsche Rijn09:16
- Woerden09:33
- Bodegraven09:42
Next service: tomorrow 08:33 from 's-Hertogenbosch · Sun 25 Oct
Next departure 08:33 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 7 full · 1 partial · 7 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 7 full · 1 partial · 29 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
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 8
- 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=3
- 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. |
|---|---|
| 08:33 | |
| 08:41 | |
| 08:48 / 08:54 | |
| 08:59 | |
| 09:05 / 09:06 | |
| 09:09 | |
| 09:13 | |
| 09:16 | |
| 09:19 / 09:23 | |
| 09:33 / 09:34 | |
| 09:42 |
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 09:48Partial coverage | 0 min | — |
| Fri 23 Oct | Woerden 09:50 | 0 min | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 09:36 | 0 min | — |
| Sat 17 Oct | Woerden 09:51 | 0 min | — |
| Fri 16 Oct | Woerden 09:51 | 0 min | — |
| Sun 11 Oct | Leiden Lammenschans 10:17 | 0 min | — |
| Sat 10 Oct | Leiden Lammenschans 10:17 | +1 min | — |
| Fri 9 Oct | Leiden Lammenschans 10:19 | 0 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 10:20 | No data | — |
| Sun 4 Oct | Leiden Lammenschans 10:17 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 10:17 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 10:20 | No data | — |
| Sun 27 Sept | Leiden Lammenschans 10:18 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 10:17 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 10:17 | No data | — |
| Sun 20 Sept | Leiden Lammenschans 10:17 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 10:18 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 10:17 | No data | — |
| Sun 13 Sept | Leiden Lammenschans 10:17 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 10:18 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 10:17 | No data | — |
| Sun 6 Sept | Leiden Lammenschans 10:18 | No data | — |
| Sat 5 Sept | Leiden Lammenschans 10:19 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 10:17 | No data | — |
| Sun 30 Aug | Leiden Lammenschans 10:17 | No data | — |
| Sat 29 Aug | Leiden Lammenschans 10:17 | No data | — |
| Fri 28 Aug | Leiden Lammenschans 10:17 | No data | — |
| Fri 21 Aug | Utrecht Vaartsche Rijn 09:36 | No data | — |
| Sun 16 Aug | Leiden Lammenschans 10:17 | No data | — |
| Sat 15 Aug | Leiden Lammenschans 10:17 | No data | — |