Train NS 8830 's-Hertogenbosch – Bodegraven

's-Hertogenbosch 09:33 → Bodegraven 10: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 10:51 No data

  1. 's-Hertogenbosch09:33
  2. Geldermalsen09:48
  3. Houten Castellum10:05
  4. Utrecht Lunetten10:13
  5. Utrecht Vaartsche Rijn10:16
  6. Woerden10:36
  7. Bodegraven10:45

Next service: tomorrow 09:33 from 's-Hertogenbosch · Tue 13 Oct

Full trip card
Next departure 09:33 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 0 full · 3 partial · 13 no data
On-time · 90 days
100%
3/3 runs under 3 min
RT coverage: 0 full · 3 partial · 49 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 so far)

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

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

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

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 100% W n=1
  • 100% T n=1
  • — 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
09:33
Zaltbommel
09:41
Geldermalsen
09:48 / 09:54
Culemborg
09:59
Houten Castellum
10:05 / 10:06
Houten
10:09
Utrecht Lunetten
10:13
Utrecht Vaartsche Rijn
10:16
Utrecht Centraal
10:19 / 10:24
Utrecht Leidsche Rijn
10:28
Woerden
10:36 / 10:37
Bodegraven
10: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 12 OctWoerden 10:51No data—
Thu 8 OctUtrecht Vaartsche Rijn 11:33Partial coverage0 min+12 min
Wed 7 OctWoerden 12:01Partial coverage0 min—
Tue 6 OctLeiden Lammenschans 11:19Partial coverage+2 min+2 min
Thu 1 OctLeiden Lammenschans 11:17No data—
Wed 30 SeptLeiden Lammenschans 11:24No data—
Tue 29 SeptLeiden Lammenschans 11:17No data—
Mon 28 SeptLeiden Lammenschans 11:18No data—
Thu 24 SeptLeiden Lammenschans 11:17No data—
Wed 23 SeptLeiden Lammenschans 11:17No data—
Tue 22 SeptLeiden Lammenschans 11:17No data—
Mon 21 SeptLeiden Lammenschans 11:17No data—
Thu 17 SeptLeiden Lammenschans 11:17No data—
Wed 16 SeptLeiden Lammenschans 11:17No data—
Tue 15 SeptLeiden Lammenschans 11:17No data—
Mon 14 SeptLeiden Lammenschans 11:18No data—
Thu 10 SeptLeiden Lammenschans 11:18No data—
Tue 8 SeptLeiden Lammenschans 11:18No data—
Mon 7 SeptLeiden Lammenschans 11:18No data—
Thu 3 SeptLeiden Lammenschans 11:20No data—
Wed 2 SeptLeiden Lammenschans 11:18No data—
Tue 1 SeptLeiden Lammenschans 11:17No data—
Mon 31 AugLeiden Lammenschans 11:17No data—
Thu 27 AugLeiden Lammenschans 11:18No data—
Wed 26 AugLeiden Lammenschans 11:17No data—
Tue 25 AugLeiden Lammenschans 11:17No data—
Mon 24 AugLeiden Lammenschans 11:17No data—
Sun 23 AugLeiden Lammenschans 11:17No data—
Sat 22 AugLeiden Lammenschans 11:19No data—
Fri 21 AugLeiden Lammenschans 11:18No data—