Train NS 6029 Den Haag Centraal – 's-Hertogenbosch

Den Haag Centraal 07:46 → 's-Hertogenbosch 09:32 Fri, Sat, Sun 1 h 46 min · 21 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: tomorrow 07:46 from Den Haag Centraal · Fri 6 Nov

Next departure 07:46 tomorrow · Den Haag Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 10 full · 1 partial · 1 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 10 full · 1 partial · 26 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 11 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:46on time on time
07:50≈ on time ≈ on time
07:53≈ on time ≈ on time
07:58≈ on time ≈ on time
08:01≈ on time ≈ on time
08:03≈ on time ≈ on time
08:13 / 08:15≈ on time ≈ on time
08:18≈ on time ≈ on time
08:27 / 08:28≈ on time ≈ on time
08:34≈ on time ≈ on time
08:37≈ on time ≈ on time
08:40≈ on time ≈ on time
08:44 / 08:50≈ on time ≈ on time
08:52≈ on time ≈ on time
08:55≈ on time ≈ on time
08:58 / 08:59≈ on time ≈ on time
09:02≈ on time ≈ on time
09:08≈ on time ≈ on time
09:15 / 09:17≈ on time ≈ on time
09:23≈ on time ≈ on time
09:32on 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 1 NovZaltbommel 09:38Partial coverage0 min—
Sat 31 OctZaltbommel 09:370 min—
Fri 30 OctZaltbommel 09:370 min—
Sun 25 OctZaltbommel 09:37No data—
Sat 24 OctTiel Passewaaij 09:460 min—
Fri 23 OctTiel Passewaaij 09:460 min—
Sun 18 OctZaltbommel 09:370 min—
Sat 17 OctZaltbommel 09:370 min—
Fri 16 OctZaltbommel 09:380 min—
Sun 11 OctZaltbommel 09:38+1 min+1 min
Sat 10 OctZaltbommel 09:370 min—
Fri 9 OctZaltbommel 09:380 min—
Mon 5 OctZaltbommel 09:37No data—
Sun 4 OctZaltbommel 09:37No data—
Sat 3 OctZaltbommel 09:37No data—
Fri 2 OctZaltbommel 09:37No data—
Sun 27 SeptZaltbommel 09:37No data—
Sat 26 SeptCulemborg 09:25No data—
Fri 25 SeptZaltbommel 09:37No data—
Sun 20 SeptZaltbommel 09:37No data—
Sat 19 SeptZaltbommel 09:37No data—
Fri 18 SeptZaltbommel 09:37No data—
Sun 13 SeptZaltbommel 09:37No data—
Sat 12 SeptZaltbommel 09:37No data—
Fri 11 SeptZaltbommel 09:39No data—
Sun 6 SeptZaltbommel 09:37No data—
Sat 5 SeptZaltbommel 09:37No data—
Fri 4 SeptZaltbommel 09:38No data—
Sun 30 AugZaltbommel 09:37No data—
Sat 29 AugZaltbommel 09:37No data—