Train NS 8818 's-Hertogenbosch – Bodegraven

's-Hertogenbosch 06:33 → Bodegraven 07: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 07:51 0 min

  1. 's-Hertogenbosch06:33
  2. Geldermalsen06:48
  3. Houten Castellum07:05
  4. Utrecht Lunetten07:13
  5. Utrecht Vaartsche Rijn07:16
  6. Woerden07:36
  7. Bodegraven07:45

Next service: tomorrow 06:33 from 's-Hertogenbosch · Tue 27 Oct

Full trip card
Next departure 06:33 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 4 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 40 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=3
  • 100% T n=3
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

StopSched.
's-Hertogenbosch
06:33
Zaltbommel
06:41
Geldermalsen
06:48 / 06:54
Culemborg
06:59
Houten Castellum
07:05 / 07:06
Houten
07:09
Utrecht Lunetten
07:13
Utrecht Vaartsche Rijn
07:16
Utrecht Centraal
07:19 / 07:24
Utrecht Leidsche Rijn
07:28
Woerden
07:36 / 07:37
Bodegraven
07:45

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.

Recent runs

DateLast stopFinalMax
Mon 26 OctWoerden 07:51Partial coverage0 min—
Thu 22 OctWoerden 07:51Partial coverage0 min—
Wed 21 OctWoerden 07:51Partial coverage0 min—
Tue 20 OctWoerden 07:51Partial coverage0 min—
Mon 19 OctUtrecht Vaartsche Rijn 07:350 min—
Thu 15 OctWoerden 07:51Partial coverage0 min—
Wed 14 OctWoerden 07:51Partial coverage0 min—
Tue 13 OctWoerden 07:51Partial coverage0 min—
Mon 12 OctWoerden 07:51Partial coverage0 min—
Thu 8 OctLeiden Lammenschans 08:18+1 min—
Wed 7 OctLeiden Lammenschans 08:19+2 min+2 min
Tue 6 OctLeiden Lammenschans 08:17+1 min—
Thu 1 OctLeiden Lammenschans 08:18No data—
Wed 30 SeptLeiden Lammenschans 08:17No data—
Tue 29 SeptLeiden Lammenschans 08:18No data—
Mon 28 SeptLeiden Lammenschans 08:18No data—
Thu 24 SeptLeiden Lammenschans 08:21No data—
Wed 23 SeptLeiden Lammenschans 08:17No data—
Tue 22 SeptLeiden Lammenschans 08:17No data—
Mon 21 SeptLeiden Lammenschans 08:18No data—
Thu 17 SeptLeiden Lammenschans 08:19No data—
Wed 16 SeptLeiden Lammenschans 08:17No data—
Tue 15 SeptLeiden Lammenschans 08:18No data—
Mon 14 SeptLeiden Lammenschans 08:20No data—
Thu 10 SeptLeiden Lammenschans 08:18No data—
Tue 8 SeptLeiden Lammenschans 08:18No data—
Mon 7 SeptLeiden Lammenschans 08:22No data—
Thu 3 SeptLeiden Lammenschans 08:19No data—
Wed 2 SeptLeiden Lammenschans 08:18No data—
Tue 1 SeptLeiden Lammenschans 08:18No data—