Train NS 6023 Utrecht Centraal – 's-Hertogenbosch

Utrecht Centraal 07:20 → 's-Hertogenbosch 08:02 Fri, Sat, Sun 0 h 42 min · 9 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November +4 min

Next service: Friday 07:20 from Utrecht Centraal · Fri 20 Nov

Next departure 07:20 Friday · Utrecht Centraal
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 7 full · 2 partial · 2 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 28 full · 3 partial · 9 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: +2 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

  • Tue 8 Sept Max en route +40 min · last fix heading to Houten +40 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Zaltbommel +4 min

Distribution · 90 days

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

  • Early 13% · 4
  • On time 81% · 25
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=2
  • 0% T n=1
  • — W n=0
  • — T n=0
  • 100% F n=12
  • 100% S n=9
  • 86% S n=7

Stops and timetable

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

Last 90 days, 31 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
07:20on time on time
07:23≈ on time ≈ on time
07:25≈ on time ≈ on time
07:29≈ on time ≈ on time
07:32≈ on time ≈ on time
07:38≈ on time ≈ on time
07:45 / 07:47≈ on time ≈ on time
07:53≈ on time ≈ on time
08:02on time on time

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
Sun 15 NovZaltbommel 08:09Partial coverage+4 min+4 min
Sat 14 NovZaltbommel 08:09+1 min+2 min
Fri 13 NovZaltbommel 08:08+1 min+1 min
Fri 6 NovZaltbommel 08:07No data—
Sun 1 NovZaltbommel 08:07Partial coverage0 min—
Sat 31 OctZaltbommel 08:070 min—
Fri 30 OctZaltbommel 08:070 min—
Sun 25 OctZaltbommel 08:07No data—
Sat 24 OctTiel Passewaaij 08:160 min—
Fri 23 OctTiel Passewaaij 08:170 min—
Sun 18 OctZaltbommel 08:070 min—
Sat 17 OctZaltbommel 08:070 min—
Fri 16 OctZaltbommel 08:070 min—
Sun 11 OctZaltbommel 08:07Partial coverage0 min—
Sat 10 OctZaltbommel 08:070 min—
Fri 9 OctZaltbommel 08:070 min—
Mon 5 OctDen Haag Ypenburg 12:200 min—
Sun 4 OctZaltbommel 08:08No data—
Sat 3 OctZaltbommel 08:07No data—
Fri 2 OctDen Haag Ypenburg 23:110 min+38 min
Mon 28 SeptUtrecht Lunetten 20:070 min—
Sun 27 SeptZaltbommel 08:07No data—
Sat 26 SeptDen Haag Ypenburg 00:39−1 min+4 min
Fri 25 SeptDen Haag Ypenburg 00:210 min+2 min
Sun 20 SeptHouten 00:05−2 min+2 min
Sat 19 SeptZaltbommel 08:07No data—
Fri 18 SeptUtrecht Vaartsche Rijn 01:19−2 min+4 min
Sun 13 SeptZaltbommel 08:07No data—
Sat 12 SeptUtrecht Vaartsche Rijn 08:350 min+2 min
Fri 11 SeptDen Haag Ypenburg 00:220 min+39 min