Train NS 8850 's-Hertogenbosch – Bodegraven

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 14:33 from 's-Hertogenbosch · Mon 16 Nov

Next departure 14:33 today · 's-Hertogenbosch
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 5 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 6 full · 11 partial · 36 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

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=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • — 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
14:33on time on time
14:41≈ on time ≈ on time
14:48 / 14:54≈ on time ≈ on time
14:59≈ on time ≈ on time
15:05 / 15:06≈ on time ≈ on time
15:09≈ on time ≈ on time
15:13≈ on time ≈ on time
15:16≈ on time ≈ on time
15:19 / 15:24≈ on time ≈ on time
15:28≈ on time ≈ on time
15:36 / 15:37≈ on time ≈ on time
15: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
Thu 12 NovWoerden 15:49Partial coverage0 min—
Wed 11 NovWoerden 15:52Partial coverage+1 min+2 min
Tue 10 NovWoerden 15:49Partial coverage0 min—
Mon 9 NovWoerden 15:50Partial coverage0 min—
Sun 8 NovWoerden 15:490 min+1 min
Sat 7 NovWoerden 15:490 min—
Thu 5 NovWoerden 15:50No data—
Wed 4 NovWoerden 15:49Partial coverage0 min—
Tue 3 NovWoerden 15:49Partial coverage0 min—
Mon 2 NovWoerden 15:49Partial coverage0 min—
Thu 29 OctWoerden 15:51Partial coverage0 min—
Wed 28 OctWoerden 15:51Partial coverage0 min—
Tue 27 OctWoerden 15:52No data—
Mon 26 OctWoerden 15:51No data—
Thu 22 OctWoerden 15:52No data—
Wed 21 OctWoerden 15:54No data—
Tue 20 OctWoerden 15:51Partial coverage0 min—
Mon 19 OctUtrecht Vaartsche Rijn 15:400 min—
Thu 15 OctWoerden 15:51No data—
Wed 14 OctWoerden 15:51No data—
Tue 13 OctWoerden 15:51No data—
Mon 12 OctWoerden 15:51Partial coverage0 min—
Thu 8 OctLeiden Lammenschans 16:170 min—
Wed 7 OctLeiden Lammenschans 16:170 min—
Tue 6 OctLeiden Lammenschans 16:170 min—
Thu 1 OctLeiden Lammenschans 16:19No data—
Wed 30 SeptLeiden Lammenschans 16:17No data—
Tue 29 SeptLeiden Lammenschans 16:17No data—
Mon 28 SeptLeiden Lammenschans 16:17No data—
Thu 24 SeptLeiden Lammenschans 16:18No data—