Train NS 6021 Utrecht Centraal – 's-Hertogenbosch

Utrecht Centraal 06:50 → 's-Hertogenbosch 07:32 Fri, Sat 0 h 42 min · 9 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Friday 06:50 from Utrecht Centraal · Fri 13 Nov

Next departure 06:50 Friday · Utrecht Centraal
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 4 full · 2 partial · 1 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 15 full · 3 partial · 7 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 '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 11% · 2
  • On time 89% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=11
  • 100% S n=6
  • — 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:50on time on time
06:52≈ on time ≈ on time
06:55≈ on time ≈ on time
06:58 / 06:59≈ on time ≈ on time
07:02≈ on time ≈ on time
07:08≈ on time ≈ on time
07:15 / 07:17≈ on time ≈ on time
07:23≈ on time ≈ +1 min
07:32on 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
Fri 6 NovZaltbommel 07:37No data—
Sat 31 OctZaltbommel 07:37Partial coverage0 min—
Fri 30 OctZaltbommel 07:38+1 min+1 min
Sat 24 OctTiel Passewaaij 07:460 min—
Fri 23 OctTiel Passewaaij 07:460 min—
Sat 17 OctZaltbommel 07:39Partial coverage+2 min+3 min
Fri 16 OctZaltbommel 07:380 min—
Sat 10 OctZaltbommel 07:37Partial coverage0 min—
Fri 9 OctZaltbommel 07:38+1 min—
Mon 5 OctUtrecht Lunetten 12:200 min+1 min
Sat 3 OctZaltbommel 07:37No data—
Fri 2 OctUtrecht Lunetten 10:520 min+2 min
Sat 26 SeptCulemborg 07:29No data—
Fri 25 SeptUtrecht Lunetten 21:47+1 min+7 min
Sat 19 SeptZaltbommel 07:37No data—
Fri 18 SeptDen Haag Ypenburg 00:22−1 min+3 min
Sat 12 SeptUtrecht Centraal 00:24−2 min+2 min
Fri 11 SeptDen Haag Ypenburg 18:330 min+3 min
Sat 5 SeptUtrecht Lunetten 00:57+1 min+4 min
Fri 4 SeptUtrecht Centraal 10:190 min+1 min
Sat 29 AugZaltbommel 07:37No data—
Fri 28 AugDen Haag Ypenburg 00:43−1 min+4 min
Fri 21 AugZaltbommel 07:37No data—
Sat 15 AugUtrecht Lunetten 07:16No data—
Fri 14 AugDen Haag Ypenburg 17:220 min—