Train NS 8868 's-Hertogenbosch – Bodegraven

's-Hertogenbosch 19:03 → Bodegraven 20: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 12 November 0 min

Next service: Monday 19:03 from 's-Hertogenbosch · Mon 16 Nov

Next departure 19:03 Monday · 's-Hertogenbosch
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 6 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 13 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: 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=5
  • 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, 17 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
19:03on time on time
19:11≈ on time ≈ on time
19:18 / 19:24≈ on time ≈ on time
19:29≈ on time ≈ on time
19:35 / 19:36≈ on time ≈ on time
19:39≈ on time ≈ on time
19:43≈ on time ≈ on time
19:46≈ on time ≈ on time
19:49 / 19:54≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20:06 / 20:07≈ on time ≈ +1 min
20: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 12 Nov— 20:140 min—
Wed 11 Nov— 20:140 min—
Tue 10 Nov— 20:170 min—
Mon 9 Nov— 20:140 min—
Sun 8 NovWoerden 20:190 min—
Sat 7 NovWoerden 20:190 min—
Thu 5 Nov— 19:49No data—
Wed 4 Nov— 20:140 min—
Tue 3 Nov— 20:14No data—
Mon 2 Nov— 20:14No data—
Thu 29 Oct— 20:160 min—
Wed 28 Oct— 20:160 min—
Tue 27 Oct— 20:17No data—
Mon 26 Oct— 20:18No data—
Thu 22 Oct— 20:17No data—
Wed 21 Oct— 20:210 min—
Tue 20 Oct— 20:210 min—
Mon 19 Oct— 19:550 min—
Thu 15 Oct— 20:190 min—
Wed 14 OctUtrecht Vaartsche Rijn 20:25No data—
Tue 13 Oct— 20:19No data—
Mon 12 Oct— 20:210 min—
Thu 8 Oct— 20:42+2 min+2 min
Wed 7 Oct— 20:39+2 min+2 min
Tue 6 Oct— 20:390 min—
Wed 26 Aug's-Hertogenbosch 19:17No data—
Sun 23 AugLeiden Lammenschans 20:47No data—
Sat 22 AugLeiden Lammenschans 20:47No data—
Fri 21 AugLeiden Lammenschans 20:46No data—
Wed 19 AugGeldermalsen 19:37No data—