Train NS 8817 Utrecht Centraal – 's-Hertogenbosch

Utrecht Centraal 06:10 → 's-Hertogenbosch 06:57 Mon, Tue, Wed, Thu 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 5 November 0 min

Next service: Monday 06:10 from Utrecht Centraal · Mon 9 Nov

Next departure 06:10 Monday · Utrecht Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 0 full · 16 partial · 1 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 0 full · 18 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
06:10on time on time
06:12— —
06:15— —
06:18 / 06:19— —
06:22— —
06:28— —
06:36 / 06:42— —
06:48— —
06:57— —

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
Thu 5 NovZaltbommel 07:02Partial coverage0 min—
Wed 4 NovZaltbommel 07:04Partial coverage+2 min+2 min
Tue 3 NovZaltbommel 07:02Partial coverage0 min—
Mon 2 NovZaltbommel 07:03No data—
Thu 29 OctZaltbommel 07:02Partial coverage0 min—
Wed 28 OctZaltbommel 07:03Partial coverage0 min—
Tue 27 OctZaltbommel 07:02Partial coverage0 min—
Mon 26 OctZaltbommel 07:02Partial coverage0 min—
Thu 22 OctZaltbommel 07:02Partial coverage0 min—
Wed 21 OctZaltbommel 07:02Partial coverage0 min—
Tue 20 OctZaltbommel 07:02Partial coverage0 min—
Mon 19 OctZaltbommel 07:02Partial coverage0 min—
Thu 15 OctZaltbommel 07:02Partial coverage0 min—
Wed 14 OctZaltbommel 07:02Partial coverage0 min—
Tue 13 OctZaltbommel 07:02Partial coverage0 min—
Mon 12 OctZaltbommel 07:02Partial coverage0 min—
Thu 8 OctZaltbommel 07:02Partial coverage0 min—
Wed 7 OctZaltbommel 07:02Partial coverage0 min—
Tue 6 OctZaltbommel 07:03Partial coverage0 min—
Thu 1 OctZaltbommel 07:02No data—
Wed 30 SeptZaltbommel 07:02No data—
Tue 29 SeptZaltbommel 07:05No data—
Mon 28 SeptZaltbommel 07:02No data—
Thu 24 SeptZaltbommel 07:02No data—
Wed 23 SeptZaltbommel 07:02No data—
Tue 22 SeptZaltbommel 07:02No data—
Mon 21 SeptZaltbommel 07:02No data—
Thu 17 SeptZaltbommel 07:02No data—
Wed 16 SeptZaltbommel 07:02No data—
Tue 15 SeptZaltbommel 07:05No data—