Train NS 8831 Bodegraven – 's-Hertogenbosch

Bodegraven 09:16 → 's-Hertogenbosch 10:27 Mon, Tue, Wed, Thu, Sat, Sun 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 09:16 from Bodegraven · Mon 16 Nov

Next departure 09:16 Monday · Bodegraven
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 6 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 9 full · 6 partial · 40 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=4
  • 100% W n=4
  • 100% T n=2
  • — F n=0
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 15 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
09:16on time on time
09:23 / 09:24≈ on time ≈ on time
09:32≈ on time ≈ on time
09:36 / 09:40≈ on time ≈ on time
09:42≈ on time ≈ on time
09:45≈ on time ≈ on time
09:48 / 09:49≈ on time ≈ on time
09:52≈ on time ≈ on time
09:58≈ on time ≈ on time
10:06 / 10:12≈ on time ≈ on time
10:18≈ on time ≈ on time
10: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 10:32Partial coverage0 min—
Wed 11 NovZaltbommel 10:33Partial coverage0 min—
Tue 10 NovZaltbommel 10:32Partial coverage0 min—
Mon 9 NovZaltbommel 10:34Partial coverage+2 min+2 min
Sun 8 NovZaltbommel 10:320 min—
Sat 7 NovZaltbommel 10:320 min—
Thu 5 NovZaltbommel 10:37No data—
Wed 4 NovZaltbommel 10:32Partial coverage0 min—
Tue 3 NovZaltbommel 10:34No data—
Mon 2 NovZaltbommel 10:32No data—
Thu 29 OctZaltbommel 10:32No data—
Wed 28 OctZaltbommel 10:320 min—
Tue 27 OctZaltbommel 10:320 min—
Mon 26 OctZaltbommel 10:320 min—
Thu 22 OctZaltbommel 10:34No data—
Wed 21 OctZaltbommel 10:32No data—
Tue 20 OctZaltbommel 10:32Partial coverage0 min—
Mon 19 OctZaltbommel 10:320 min—
Thu 15 OctWoerden 10:58No data—
Wed 14 OctZaltbommel 10:34No data—
Tue 13 OctZaltbommel 10:32No data—
Mon 12 OctZaltbommel 10:32No data—
Thu 8 OctZaltbommel 10:320 min—
Wed 7 OctZaltbommel 10:350 min—
Tue 6 OctZaltbommel 10:320 min—
Thu 1 OctZaltbommel 10:33No data—
Wed 30 SeptZaltbommel 10:34No data—
Tue 29 SeptZaltbommel 10:32No data—
Mon 28 SeptZaltbommel 10:44No data—
Thu 24 SeptZaltbommel 10:32No data—