Train NS 8823 Bodegraven – 's-Hertogenbosch

Bodegraven 07:16 → 's-Hertogenbosch 08:27 Mon, Tue, Wed, Thu, Sat 1 h 11 min · 12 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 12 November 0 min

Next service: Monday 07:16 from Bodegraven · Mon 16 Nov

Full trip card
Next departure 07:16 Monday · Bodegraven
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 4 full · 12 partial · 2 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 7 full · 14 partial · 32 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 's-Hertogenbosch, 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

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

  • Early 0% · 0
  • On time 100% · 21
  • 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=4
  • 100% W n=6
  • 100% T n=5
  • — 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, 21 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
Bodegraven
07:16on time on time
Woerden
07:23 / 07:24≈ on time ≈ on time
Utrecht Leidsche Rijn
07:32≈ on time ≈ on time
Utrecht Centraal
07:36 / 07:40≈ on time ≈ on time
Utrecht Vaartsche Rijn
07:42≈ on time ≈ on time
Utrecht Lunetten
07:45≈ on time ≈ on time
Houten
07:48 / 07:49≈ on time ≈ on time
Houten Castellum
07:52≈ on time ≈ on time
Culemborg
07:58≈ on time ≈ on time
Geldermalsen
08:06 / 08:12≈ on time ≈ on time
Zaltbommel
08:18≈ on time ≈ on time
's-Hertogenbosch
08:27on time on time

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
Thu 12 NovZaltbommel 08:32Partial coverage0 min—
Wed 11 NovZaltbommel 08:33Partial coverage0 min—
Tue 10 NovZaltbommel 08:33Partial coverage0 min—
Mon 9 NovZaltbommel 08:32Partial coverage0 min—
Sat 7 NovZaltbommel 08:320 min—
Thu 5 NovZaltbommel 08:32Partial coverage0 min—
Wed 4 NovZaltbommel 08:32Partial coverage0 min—
Tue 3 NovZaltbommel 08:32Partial coverage0 min—
Mon 2 NovZaltbommel 08:32Partial coverage0 min—
Thu 29 OctZaltbommel 08:34Partial coverage0 min—
Wed 28 OctZaltbommel 08:32Partial coverage0 min—
Tue 27 OctZaltbommel 08:32No data—
Mon 26 OctZaltbommel 08:340 min—
Thu 22 OctZaltbommel 08:33Partial coverage0 min—
Wed 21 OctZaltbommel 08:320 min—
Tue 20 OctZaltbommel 08:32Partial coverage0 min—
Mon 19 OctZaltbommel 08:320 min—
Thu 15 OctZaltbommel 08:34No data—
Wed 14 OctZaltbommel 08:32Partial coverage0 min—
Tue 13 OctZaltbommel 08:33No data—
Mon 12 OctZaltbommel 08:32Partial coverage0 min—
Thu 8 OctZaltbommel 08:330 min—
Wed 7 OctZaltbommel 08:320 min—
Tue 6 OctZaltbommel 08:320 min—
Thu 1 OctZaltbommel 08:32No data—
Wed 30 SeptZaltbommel 08:32No data—
Tue 29 SeptZaltbommel 08:32No data—
Mon 28 SeptZaltbommel 08:33No data—
Thu 24 SeptZaltbommel 08:34No data—
Wed 23 SeptZaltbommel 08:34No data—