Train NS 8821 Bodegraven – 's-Hertogenbosch

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

Running now · updated 06:42

Position estimated from the timetable

Heading to 's-Hertogenbosch 0 min

Estimated arrival at 's-Hertogenbosch 07:57

  1. Bodegraven06:46
  2. Utrecht Leidsche Rijn07:02
  3. Utrecht Vaartsche Rijn07:12
  4. Houten07:18
  5. Houten Castellum07:22
  6. Geldermalsen07:36
  7. 's-Hertogenbosch07:57

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 19 runs arrived on time.

On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 1 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 9 full · 18 partial · 26 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: +2 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

  • Wed 4 Nov Max en route +3 min · last fix heading to Zaltbommel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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