Train NS 8829 Bodegraven – 's-Hertogenbosch

Bodegraven 08:46 → 's-Hertogenbosch 09:57 Mon, Tue, Wed, Thu 1 h 11 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zaltbommel at 10:04 +2 min

  1. Bodegraven08:46
  2. Utrecht Leidsche Rijn09:02
  3. Utrecht Vaartsche Rijn09:12
  4. Houten09:18
  5. Houten Castellum09:22
  6. Zaltbommel09:48
  7. 's-Hertogenbosch09:57

Next service: tomorrow 08:46 from Bodegraven · Tue 17 Nov

Next departure 08:46 tomorrow · Bodegraven
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 3 full · 9 partial · 7 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 6 full · 11 partial · 37 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: +1 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=2
  • 100% W n=5
  • 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, 17 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
08:46on time on time
08:53 / 08:54≈ on time ≈ on time
09:02≈ on time ≈ on time
09:06 / 09:10≈ on time ≈ on time
09:12≈ on time ≈ on time
09:15≈ on time ≈ on time
09:18 / 09:19≈ on time ≈ on time
09:22≈ on time ≈ on time
09:28≈ on time ≈ on time
09:36 / 09:42≈ on time ≈ on time
09:48≈ on time ≈ on time
09:57on 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 NovZaltbommel 10:04Partial coverage+2 min+2 min
Thu 12 NovZaltbommel 10:02Partial coverage0 min—
Wed 11 NovZaltbommel 10:03Partial coverage0 min—
Tue 10 NovZaltbommel 10:02Partial coverage0 min—
Mon 9 NovZaltbommel 10:03Partial coverage0 min—
Sun 8 NovZaltbommel 10:03+1 min+1 min
Sat 7 NovZaltbommel 10:020 min—
Thu 5 NovZaltbommel 10:04No data—
Wed 4 NovZaltbommel 10:02Partial coverage0 min—
Tue 3 NovZaltbommel 10:02No data—
Mon 2 NovZaltbommel 10:02Partial coverage0 min—
Thu 29 OctZaltbommel 10:02No data—
Wed 28 OctZaltbommel 10:02Partial coverage0 min—
Tue 27 OctZaltbommel 10:02No data—
Mon 26 OctZaltbommel 10:02Partial coverage0 min—
Thu 22 OctZaltbommel 10:02No data—
Wed 21 OctZaltbommel 10:02No data—
Tue 20 OctZaltbommel 10:02No data—
Mon 19 OctZaltbommel 10:040 min—
Thu 15 OctCulemborg 10:58No data—
Wed 14 OctZaltbommel 10:02Partial coverage0 min—
Tue 13 OctZaltbommel 10:03No data—
Mon 12 OctZaltbommel 10:03Partial coverage0 min—
Thu 8 OctZaltbommel 10:020 min—
Wed 7 OctZaltbommel 10:020 min—
Tue 6 OctZaltbommel 10:020 min—
Thu 1 OctZaltbommel 10:02No data—
Wed 30 SeptZaltbommel 10:03No data—
Tue 29 SeptZaltbommel 10:02No data—
Mon 28 SeptZaltbommel 10:02No data—