Train NS 8834 's-Hertogenbosch – Bodegraven

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 10:33 from 's-Hertogenbosch · Sun 8 Nov

Next departure 10:33 today · 's-Hertogenbosch
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 10 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 43 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 Bodegraven, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 10 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
10:33on time on time
10:41≈ on time ≈ on time
10:48 / 10:54≈ on time ≈ on time
10:59≈ on time ≈ on time
11:05 / 11:06≈ on time ≈ on time
11:09≈ on time ≈ on time
11:13≈ on time ≈ on time
11:16≈ on time ≈ on time
11:19 / 11:25≈ on time ≈ on time
11:35 / 11:37≈ on time ≈ on time
11:45on 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
Sat 7 NovWoerden 11:49Partial coverage0 min—
Thu 5 NovWoerden 11:49No data—
Wed 4 NovWoerden 11:490 min—
Tue 3 NovWoerden 11:49No data—
Mon 2 NovWoerden 11:54No data—
Thu 29 OctWoerden 11:510 min—
Wed 28 OctWoerden 11:520 min—
Tue 27 OctWoerden 11:510 min—
Mon 26 OctWoerden 11:51No data—
Thu 22 OctWoerden 11:52No data—
Wed 21 OctWoerden 11:51No data—
Tue 20 OctWoerden 11:510 min—
Mon 19 OctUtrecht Vaartsche Rijn 11:350 min—
Thu 15 OctWoerden 11:51No data—
Wed 14 OctWoerden 11:51No data—
Tue 13 OctWoerden 11:51No data—
Mon 12 OctWoerden 11:51No data—
Thu 8 OctLeiden Lammenschans 12:170 min—
Wed 7 OctLeiden Lammenschans 12:190 min—
Tue 6 OctLeiden Lammenschans 12:170 min—
Thu 1 OctLeiden Lammenschans 12:17No data—
Wed 30 SeptLeiden Lammenschans 12:19No data—
Tue 29 SeptLeiden Lammenschans 12:17No data—
Mon 28 SeptLeiden Lammenschans 12:17No data—
Thu 24 SeptLeiden Lammenschans 12:17No data—
Wed 23 SeptLeiden Lammenschans 12:17No data—
Tue 22 SeptLeiden Lammenschans 12:17No data—
Mon 21 SeptLeiden Lammenschans 12:17No data—
Thu 17 SeptLeiden Lammenschans 12:18No data—
Wed 16 SeptLeiden Lammenschans 12:17No data—