Train NS 8826 's-Hertogenbosch – Bodegraven

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

✓ Today’s run finished

Today, last fix heading to Woerden at 09:49 0 min

  1. 's-Hertogenbosch08:33
  2. Geldermalsen08:48
  3. Houten Castellum09:05
  4. Utrecht Lunetten09:13
  5. Utrecht Vaartsche Rijn09:16
  6. Woerden09:36
  7. Bodegraven09:45

Next service: tomorrow 08:33 from 's-Hertogenbosch · Tue 17 Nov

Next departure 08:33 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 4 full · 12 partial · 3 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 7 full · 14 partial · 33 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

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

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