Train NS 8856 's-Hertogenbosch – Bodegraven

's-Hertogenbosch 16:03 → Bodegraven 17:15 Mon, Tue, Wed, Thu 1 h 12 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Woerden at 17:21 0 min

  1. 's-Hertogenbosch16:03
  2. Geldermalsen16:18
  3. Houten Castellum16:35
  4. Utrecht Lunetten16:43
  5. Utrecht Vaartsche Rijn16:46
  6. Woerden17:06
  7. Bodegraven17:15

Next service: tomorrow 16:03 from 's-Hertogenbosch · Thu 29 Oct

Full trip card
Next departure 16:03 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 8 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 43 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 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

9 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 100% · 9
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 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 (12 stops).

StopSched.
's-Hertogenbosch
16:03
Zaltbommel
16:11
Geldermalsen
16:18 / 16:24
Culemborg
16:29
Houten Castellum
16:35 / 16:36
Houten
16:39
Utrecht Lunetten
16:43
Utrecht Vaartsche Rijn
16:46
Utrecht Centraal
16:49 / 16:54
Utrecht Leidsche Rijn
16:58
Woerden
17:06 / 17:07
Bodegraven
17:15

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

DateLast stopFinalMax
Wed 28 OctWoerden 17:21Partial coverage0 min—
Tue 27 OctWoerden 17:210 min—
Mon 26 OctWoerden 17:210 min—
Thu 22 OctWoerden 17:21No data—
Wed 21 OctWoerden 17:17No data—
Tue 20 OctWoerden 17:21No data—
Mon 19 OctUtrecht Vaartsche Rijn 17:060 min—
Thu 15 OctWoerden 17:18No data—
Wed 14 OctWoerden 17:210 min—
Tue 13 OctWoerden 17:22No data—
Mon 12 OctWoerden 17:210 min—
Thu 8 OctLeiden Lammenschans 17:550 min+8 min
Wed 7 OctLeiden Lammenschans 17:460 min—
Tue 6 OctLeiden Lammenschans 17:500 min+6 min
Thu 1 OctLeiden Lammenschans 17:46No data—
Wed 30 SeptLeiden Lammenschans 17:46No data—
Tue 29 SeptLeiden Lammenschans 17:46No data—
Mon 28 SeptLeiden Lammenschans 17:46No data—
Thu 24 SeptLeiden Lammenschans 17:46No data—
Wed 23 SeptLeiden Lammenschans 17:46No data—
Tue 22 SeptLeiden Lammenschans 17:46No data—
Mon 21 SeptLeiden Lammenschans 17:46No data—
Thu 17 SeptLeiden Lammenschans 17:46No data—
Wed 16 SeptLeiden Lammenschans 17:46No data—
Tue 15 SeptLeiden Lammenschans 17:46No data—
Mon 14 SeptLeiden Lammenschans 17:46No data—
Thu 10 SeptLeiden Lammenschans 17:47No data—
Tue 8 SeptLeiden Lammenschans 17:47No data—
Mon 7 SeptLeiden Lammenschans 17:46No data—
Thu 3 SeptLeiden Lammenschans 17:46No data—