Train NS 8852 's-Hertogenbosch – Bodegraven

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

It does not run today

Last recorded run: Thursday 5 November No data

Next service: tomorrow 15:03 from 's-Hertogenbosch · Sat 7 Nov

Next departure 15:03 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 3 full · 7 partial · 7 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 5 full · 7 partial · 41 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • — 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, 12 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
15:03on time on time
15:11≈ on time ≈ on time
15:18 / 15:24≈ on time ≈ on time
15:29≈ on time ≈ on time
15:35 / 15:36≈ on time ≈ +1 min
15:39≈ on time ≈ +1 min
15:43≈ on time ≈ +1 min
15:46≈ on time ≈ +1 min
15:49 / 15:54≈ on time ≈ +1 min
15:58≈ on time ≈ +1 min
16:06 / 16:07≈ on time ≈ +1 min
16:15on 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
Thu 5 NovWoerden 16:22No data—
Wed 4 NovWoerden 16:22Partial coverage+1 min+1 min
Tue 3 NovWoerden 16:19No data—
Mon 2 NovWoerden 16:19No data—
Thu 29 OctWoerden 16:21No data—
Wed 28 OctWoerden 16:21Partial coverage0 min—
Tue 27 OctWoerden 16:210 min—
Mon 26 OctWoerden 16:21Partial coverage0 min—
Thu 22 OctWoerden 16:22No data—
Wed 21 OctWoerden 16:24Partial coverage0 min—
Tue 20 OctWoerden 16:28Partial coverage0 min—
Mon 19 OctUtrecht Vaartsche Rijn 16:060 min—
Thu 15 OctWoerden 16:24Partial coverage0 min—
Wed 14 OctWoerden 16:21No data—
Tue 13 OctWoerden 16:21No data—
Mon 12 OctWoerden 16:21Partial coverage0 min—
Thu 8 OctLeiden Lammenschans 16:46+1 min—
Wed 7 OctLeiden Lammenschans 16:46+2 min+2 min
Tue 6 OctLeiden Lammenschans 16:470 min—
Thu 1 OctLeiden Lammenschans 16:48No data—
Wed 30 SeptLeiden Lammenschans 16:47No data—
Tue 29 SeptLeiden Lammenschans 16:50No data—
Mon 28 SeptLeiden Lammenschans 16:49No data—
Thu 24 SeptLeiden Lammenschans 16:46No data—
Wed 23 SeptLeiden Lammenschans 16:47No data—
Tue 22 SeptLeiden Lammenschans 16:48No data—
Mon 21 SeptLeiden Lammenschans 16:48No data—
Thu 17 SeptLeiden Lammenschans 16:48No data—
Wed 16 SeptLeiden Lammenschans 16:48No data—
Tue 15 SeptLeiden Lammenschans 16:50No data—