Train NS 6035 Den Haag Centraal – 's-Hertogenbosch

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: Friday 09:16 from Den Haag Centraal · Fri 13 Nov

Next departure 09:16 Friday · Den Haag Centraal
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 4 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 7 full · 2 partial · 29 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 9
  • 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=2
  • 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, 9 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
09:16on time on time
09:20≈ on time ≈ on time
09:23≈ on time ≈ on time
09:28≈ on time ≈ on time
09:31≈ on time ≈ on time
09:33≈ on time ≈ on time
09:43 / 09:45≈ on time ≈ +1 min
09:48≈ on time ≈ +1 min
09:57 / 09:58≈ on time ≈ +1 min
10:04≈ on time ≈ +1 min
10:07≈ on time ≈ +1 min
10:10≈ on time ≈ +1 min
10:14 / 10:20≈ on time ≈ +1 min
10:22≈ on time ≈ +2 min
10:25≈ on time ≈ +2 min
10:28 / 10:29≈ on time ≈ +2 min
10:32≈ on time ≈ +2 min
10:38≈ on time ≈ +2 min
10:45 / 10:47≈ on time ≈ +2 min
10:53≈ on time ≈ +2 min
11:02on time +3 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 11:07No data—
Sun 1 NovZaltbommel 11:09Partial coverage+1 min—
Sat 31 OctZaltbommel 11:070 min—
Fri 30 OctZaltbommel 11:07No data—
Sun 25 OctZaltbommel 11:07No data—
Sat 24 OctTiel Passewaaij 11:19+3 min+3 min
Fri 23 OctTiel Passewaaij 11:160 min—
Sun 18 OctZaltbommel 11:09+3 min+3 min
Sat 17 OctZaltbommel 11:070 min—
Fri 16 OctZaltbommel 11:07No data—
Sun 11 OctZaltbommel 11:07Partial coverage0 min—
Sat 10 OctZaltbommel 11:080 min—
Fri 9 OctZaltbommel 11:070 min—
Mon 5 OctZaltbommel 11:07No data—
Sun 4 OctZaltbommel 11:07No data—
Sat 3 OctZaltbommel 11:07No data—
Fri 2 OctZaltbommel 11:07No data—
Sun 27 SeptZaltbommel 11:07No data—
Sat 26 SeptCulemborg 10:54No data—
Fri 25 SeptZaltbommel 11:07No data—
Sun 20 SeptZaltbommel 11:07No data—
Sat 19 SeptZaltbommel 11:07No data—
Fri 18 SeptZaltbommel 11:07No data—
Sun 13 SeptZaltbommel 11:07No data—
Sat 12 SeptZaltbommel 11:18No data—
Fri 11 SeptZaltbommel 11:07No data—
Sun 6 SeptZaltbommel 11:07No data—
Sat 5 SeptZaltbommel 11:07No data—
Fri 4 SeptZaltbommel 11:09No data—
Sun 30 AugZaltbommel 11:07No data—