Train NS 8862 's-Hertogenbosch – Bodegraven

's-Hertogenbosch 17:33 → Bodegraven 18:45 Mon, Tue, Wed, Thu 1 h 12 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 17:33 from 's-Hertogenbosch · Tue 17 Nov

Next departure 17:33 today · 's-Hertogenbosch
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 6 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 6 full · 12 partial · 35 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 Bodegraven, 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 7 Oct Max en route +6 min · last fix heading to Houten +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 67% W n=3
  • 100% T n=4
  • — 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, 18 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
17:33on time on time
17:41≈ on time ≈ on time
17:48 / 17:54≈ on time ≈ +1 min
17:59≈ on time ≈ +1 min
18:05 / 18:06≈ on time ≈ +1 min
18:09≈ on time ≈ +2 min
18:13≈ on time ≈ +2 min
18:16≈ on time ≈ +2 min
18:19 / 18:24≈ on time ≈ +2 min
18:28≈ on time ≈ +2 min
18:36 / 18:37≈ on time ≈ +3 min
18:45on time +3 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 NovUtrecht Centraal 18:45Partial coverage0 min—
Thu 12 NovUtrecht Vaartsche Rijn 18:48Partial coverage+1 min+1 min
Wed 11 NovUtrecht Lunetten 18:44Partial coverage0 min—
Tue 10 NovUtrecht Vaartsche Rijn 18:47Partial coverage+1 min—
Mon 9 NovUtrecht Lunetten 18:47Partial coverage0 min—
Sun 8 NovWoerden 18:520 min+4 min
Sat 7 NovWoerden 18:490 min—
Thu 5 NovUtrecht Lunetten 18:44No data—
Wed 4 NovUtrecht Lunetten 18:47No data—
Tue 3 NovHouten 18:49No data—
Mon 2 NovHouten 18:23No data—
Thu 29 OctCulemborg 18:47Partial coverage+1 min—
Wed 28 OctUtrecht Lunetten 18:46Partial coverage0 min—
Tue 27 OctCulemborg 18:47No data—
Mon 26 OctHouten 18:23Partial coverage0 min—
Thu 22 OctWoerden 18:51Partial coverage0 min—
Wed 21 OctWoerden 18:51No data—
Tue 20 OctWoerden 18:50Partial coverage0 min—
Mon 19 OctUtrecht Vaartsche Rijn 18:350 min—
Thu 15 OctUtrecht Leidsche Rijn 18:42No data—
Wed 14 OctWoerden 18:51No data—
Tue 13 OctWoerden 18:50Partial coverage0 min—
Mon 12 OctUtrecht Centraal 19:11Partial coverage0 min—
Thu 8 OctCulemborg 19:090 min—
Wed 7 OctHouten 19:20+6 min+6 min
Tue 6 OctCulemborg 18:130 min—
Thu 1 OctHouten Castellum 18:20No data—
Wed 30 SeptHouten 18:18No data—
Tue 29 SeptHouten Castellum 18:20No data—
Mon 28 SeptCulemborg 18:13No data—