Train NS 8856 's-Hertogenbosch – Utrecht Centraal
✓ Today’s run finished
Today, last fix heading to Utrecht Vaartsche Rijn at 17:06 0 min
- 's-Hertogenbosch16:03
- Zaltbommel16:11
- Culemborg16:30
- Houten Castellum16:36
- Houten16:44
- Utrecht Vaartsche Rijn16:51
- Utrecht Centraal16:54
Next service: tomorrow 16:03 from 's-Hertogenbosch · Tue 20 Oct
Next departure 16:03 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 10 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min
Last 30 days
Arrival delay at Utrecht Centraal, 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
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 6
- 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=1
- 100% W n=2
- 100% T n=1
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
| Stop | Sched. |
|---|---|
| 16:03 | |
| 16:11 | |
| 16:18 / 16:24 | |
| 16:30 | |
| 16:36 / 16:41 | |
| 16:44 | |
| 16:48 | |
| 16:51 | |
| 16:54 |
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 |
|---|---|---|---|
| Mon 19 Oct | Utrecht Vaartsche Rijn 17:06Partial coverage | 0 min | — |
| Thu 15 Oct | Woerden 17:18 | No data | — |
| Wed 14 Oct | Woerden 17:21 | 0 min | — |
| Tue 13 Oct | Woerden 17:22 | No data | — |
| Mon 12 Oct | Woerden 17:21 | 0 min | — |
| Thu 8 Oct | Leiden Lammenschans 17:55 | 0 min | +8 min |
| Wed 7 Oct | Leiden Lammenschans 17:46 | 0 min | — |
| Tue 6 Oct | Leiden Lammenschans 17:50 | 0 min | +6 min |
| Thu 1 Oct | Leiden Lammenschans 17:46 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 17:46 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 17:46 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 17:46 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 17:46 | No data | — |
| Wed 23 Sept | Leiden Lammenschans 17:46 | No data | — |
| Tue 22 Sept | Leiden Lammenschans 17:46 | No data | — |
| Mon 21 Sept | Leiden Lammenschans 17:46 | No data | — |
| Thu 17 Sept | Leiden Lammenschans 17:46 | No data | — |
| Wed 16 Sept | Leiden Lammenschans 17:46 | No data | — |
| Tue 15 Sept | Leiden Lammenschans 17:46 | No data | — |
| Mon 14 Sept | Leiden Lammenschans 17:46 | No data | — |
| Thu 10 Sept | Leiden Lammenschans 17:47 | No data | — |
| Tue 8 Sept | Leiden Lammenschans 17:47 | No data | — |
| Mon 7 Sept | Leiden Lammenschans 17:46 | No data | — |
| Thu 3 Sept | Leiden Lammenschans 17:46 | No data | — |
| Wed 2 Sept | Leiden Lammenschans 17:46 | No data | — |
| Tue 1 Sept | Leiden Lammenschans 17:46 | No data | — |
| Mon 31 Aug | Leiden Lammenschans 17:46 | No data | — |
| Thu 27 Aug | Leiden Lammenschans 17:46 | No data | — |
| Wed 26 Aug | Leiden Lammenschans 17:47 | No data | — |
| Tue 25 Aug | Leiden Lammenschans 17:46 | No data | — |