Train NS 8838 's-Hertogenbosch – Bodegraven

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 11:33 from 's-Hertogenbosch · Tue 17 Nov

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

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

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

On-time by weekday

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