Train NS 8857 Bodegraven – 's-Hertogenbosch

Bodegraven 15:46 → 's-Hertogenbosch 16:59 Mon, Tue, Wed, Thu 1 h 13 min · 12 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zaltbommel at 17:09 +3 min

  1. Bodegraven15:46
  2. Utrecht Leidsche Rijn16:02
  3. Utrecht Vaartsche Rijn16:12
  4. Houten16:18
  5. Houten Castellum16:22
  6. Zaltbommel16:50
  7. 's-Hertogenbosch16:59

Next service: tomorrow 15:46 from Bodegraven · Tue 17 Nov

Next departure 15:46 tomorrow · Bodegraven
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 11 full · 4 partial · 4 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 16 full · 4 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at 's-Hertogenbosch, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 7 Nov Max en route +9 min · last fix heading to Zaltbommel +9 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Zaltbommel +4 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Zaltbommel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 75% T n=4
  • 100% W n=3
  • 100% T n=5
  • — F n=0
  • 0% 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, 20 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
15:46on time on time
15:53 / 15:54≈ on time ≈ on time
16:02≈ on time ≈ on time
16:06 / 16:10≈ on time ≈ on time
16:12≈ on time ≈ +1 min
16:15≈ on time ≈ +1 min
16:18 / 16:19≈ on time ≈ +1 min
16:22≈ on time ≈ +1 min
16:28≈ on time ≈ +1 min
16:36 / 16:44≈ on time ≈ +1 min
16:50≈ on time ≈ +1 min
16:59on 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 NovZaltbommel 17:09Partial coverage+3 min+3 min
Thu 12 NovZaltbommel 17:04Partial coverage+1 min+1 min
Wed 11 NovZaltbommel 17:04Partial coverage0 min—
Tue 10 NovZaltbommel 17:04Partial coverage+4 min+4 min
Mon 9 NovZaltbommel 17:03+3 min+3 min
Sun 8 NovZaltbommel 17:030 min—
Sat 7 NovZaltbommel 17:14+9 min+9 min
Thu 5 NovZaltbommel 17:020 min—
Wed 4 NovZaltbommel 17:040 min—
Tue 3 NovZaltbommel 17:07No data—
Mon 2 NovZaltbommel 17:040 min—
Thu 29 OctZaltbommel 17:100 min—
Wed 28 OctZaltbommel 17:02No data—
Tue 27 OctZaltbommel 17:020 min—
Mon 26 OctZaltbommel 17:020 min—
Thu 22 OctZaltbommel 17:02No data—
Wed 21 OctZaltbommel 17:10No data—
Tue 20 OctZaltbommel 17:020 min—
Mon 19 OctZaltbommel 17:020 min—
Thu 15 OctZaltbommel 17:190 min—
Wed 14 OctZaltbommel 17:02No data—
Tue 13 OctZaltbommel 17:02No data—
Mon 12 OctZaltbommel 17:020 min—
Thu 8 OctZaltbommel 17:020 min—
Wed 7 OctZaltbommel 17:020 min—
Tue 6 OctZaltbommel 17:020 min—
Thu 1 OctZaltbommel 17:02No data—
Wed 30 SeptZaltbommel 17:01No data—
Tue 29 SeptZaltbommel 17:02No data—
Mon 28 SeptZaltbommel 17:07No data—