Train NS 8863 Bodegraven – 's-Hertogenbosch

Bodegraven 17:16 → 's-Hertogenbosch 18:27 Mon, Tue, Wed, Thu, Sat, Sun 1 h 11 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:16 from Bodegraven · Sat 7 Nov

Next departure 17:16 today · Bodegraven
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 8 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 6 full · 5 partial · 42 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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:16on time on time
17:23 / 17:24≈ on time ≈ on time
17:32≈ on time ≈ on time
17:36 / 17:40≈ on time ≈ on time
17:42≈ on time ≈ on time
17:45≈ on time ≈ on time
17:48 / 17:49≈ on time ≈ on time
17:52≈ on time ≈ on time
17:58≈ on time ≈ on time
18:06 / 18:12≈ on time ≈ on time
18:18≈ on time ≈ on time
18: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 5 NovGeldermalsen 18:28No data—
Wed 4 NovGeldermalsen 18:29Partial coverage0 min—
Tue 3 NovGeldermalsen 18:28No data—
Mon 2 NovCulemborg 18:28Partial coverage+1 min—
Thu 29 OctCulemborg 18:30No data—
Wed 28 OctGeldermalsen 18:300 min—
Tue 27 OctCulemborg 18:39No data—
Mon 26 OctCulemborg 18:280 min—
Thu 22 OctZaltbommel 18:32No data—
Wed 21 OctZaltbommel 18:32No data—
Tue 20 OctZaltbommel 18:32Partial coverage0 min—
Mon 19 OctZaltbommel 18:320 min—
Thu 15 OctZaltbommel 18:32No data—
Wed 14 OctZaltbommel 18:32No data—
Tue 13 OctUtrecht Leidsche Rijn 18:47Partial coverage0 min—
Mon 12 OctZaltbommel 18:45Partial coverage0 min—
Thu 8 OctCulemborg 18:290 min—
Wed 7 OctCulemborg 18:120 min—
Tue 6 OctCulemborg 18:280 min—
Thu 1 OctCulemborg 18:12No data—
Wed 30 SeptCulemborg 18:12No data—
Tue 29 SeptCulemborg 18:12No data—
Mon 28 SeptCulemborg 18:12No data—
Thu 24 SeptHouten Castellum 18:07No data—
Wed 23 SeptCulemborg 18:12No data—
Tue 22 SeptCulemborg 18:08No data—
Mon 21 SeptCulemborg 18:12No data—
Thu 17 SeptCulemborg 18:12No data—
Wed 16 SeptCulemborg 18:12No data—
Tue 15 SeptCulemborg 18:08No data—