Train NS 8825 Bodegraven – 's-Hertogenbosch

Bodegraven 07:46 → 's-Hertogenbosch 08: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 09:03 0 min

  1. Bodegraven07:46
  2. Utrecht Leidsche Rijn08:02
  3. Utrecht Vaartsche Rijn08:12
  4. Houten08:18
  5. Houten Castellum08:22
  6. Zaltbommel08:48
  7. 's-Hertogenbosch08:57

Next service: tomorrow 07:46 from Bodegraven · Wed 18 Nov

Next departure 07:46 tomorrow · Bodegraven
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 8 full · 7 partial · 5 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 10 full · 10 partial · 34 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 's-Hertogenbosch, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 16 Nov Max en route +3 min · last fix heading to Zaltbommel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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