Train NS 8816 's-Hertogenbosch – Bodegraven

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 06:03 from 's-Hertogenbosch · Tue 17 Nov

Next departure 06:03 today · 's-Hertogenbosch
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 6 full · 11 partial · 1 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 10 full · 14 partial · 27 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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • — F n=0
  • 100% S n=1
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

Last 90 days, 24 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
06:03on time on time
06:11≈ on time ≈ on time
06:18 / 06:24≈ on time ≈ on time
06:29≈ on time ≈ on time
06:35 / 06:36≈ on time ≈ on time
06:39≈ on time ≈ on time
06:43≈ on time ≈ +1 min
06:46≈ on time ≈ +1 min
06:49 / 06:54≈ on time ≈ +1 min
06:58≈ on time ≈ +1 min
07:06 / 07:07≈ on time ≈ +1 min
07:15on time +1 min

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.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Mon 16 NovWoerden 07:22Partial coverage+1 min+1 min
Thu 12 NovWoerden 07:190 min—
Wed 11 NovWoerden 07:19Partial coverage0 min—
Tue 10 NovWoerden 07:19Partial coverage0 min—
Mon 9 NovWoerden 07:23Partial coverage+2 min+2 min
Sat 7 NovWoerden 07:190 min—
Thu 5 NovWoerden 07:220 min—
Wed 4 NovWoerden 07:19Partial coverage0 min—
Tue 3 NovWoerden 07:19Partial coverage0 min—
Mon 2 NovWoerden 07:19No data—
Thu 29 OctWoerden 07:210 min—
Wed 28 OctWoerden 07:21Partial coverage0 min—
Tue 27 OctWoerden 07:21Partial coverage0 min—
Mon 26 OctWoerden 07:21Partial coverage0 min—
Thu 22 OctWoerden 07:210 min—
Wed 21 OctWoerden 07:21Partial coverage0 min—
Tue 20 OctWoerden 07:21Partial coverage0 min—
Mon 19 OctUtrecht Vaartsche Rijn 07:06+1 min+1 min
Thu 15 OctWoerden 07:210 min—
Wed 14 OctWoerden 07:21Partial coverage0 min—
Tue 13 OctWoerden 07:21Partial coverage0 min—
Mon 12 OctWoerden 07:22Partial coverage+1 min+2 min
Thu 8 OctLeiden Lammenschans 07:480 min+1 min
Wed 7 OctLeiden Lammenschans 07:48+1 min+2 min
Tue 6 OctLeiden Lammenschans 07:47+1 min—
Thu 1 OctLeiden Lammenschans 07:47No data—
Wed 30 SeptLeiden Lammenschans 07:47No data—
Tue 29 SeptLeiden Lammenschans 07:48No data—
Mon 28 SeptLeiden Lammenschans 07:47No data—
Thu 24 SeptLeiden Lammenschans 07:56No data—