Train NS 6065 Den Haag Centraal – 's-Hertogenbosch

Den Haag Centraal 16:43 → 's-Hertogenbosch 18:32 Fri, Sat, Sun 1 h 49 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 16:43 from Den Haag Centraal · Sun 15 Nov

Next departure 16:43 today · Den Haag Centraal
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 4 full · 6 partial · 1 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 8 full · 10 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Distribution · 90 days

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

  • Early 6% · 1
  • On time 94% · 17
  • 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=8
  • 100% S n=5
  • 100% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (21 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
16:43on time on time
16:47≈ on time ≈ on time
16:50≈ on time ≈ on time
16:55≈ on time ≈ on time
16:58≈ on time ≈ on time
17:00≈ on time ≈ on time
17:10 / 17:15≈ on time ≈ +1 min
17:18≈ on time ≈ +1 min
17:27 / 17:28≈ on time ≈ +1 min
17:34≈ on time ≈ +1 min
17:37≈ on time ≈ +1 min
17:40≈ on time ≈ +1 min
17:44 / 17:50≈ on time ≈ +1 min
17:52≈ on time ≈ +1 min
17:55≈ on time ≈ +2 min
17:58 / 17:59≈ on time ≈ +2 min
18:02≈ on time ≈ +2 min
18:08≈ on time ≈ +2 min
18:15 / 18:17≈ on time ≈ +2 min
18:23≈ on time ≈ +2 min
18:32on time +2 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
Sat 14 NovZaltbommel 18:37Partial coverage0 min—
Fri 13 NovZaltbommel 18:38Partial coverage+3 min+3 min
Fri 6 NovZaltbommel 18:37Partial coverage0 min—
Sun 1 NovZaltbommel 18:37Partial coverage0 min—
Sat 31 OctZaltbommel 18:37Partial coverage0 min—
Fri 30 OctZaltbommel 18:37Partial coverage0 min—
Sun 25 OctZaltbommel 18:37No data—
Sat 24 OctTiel Passewaaij 18:460 min—
Fri 23 OctTiel Passewaaij 18:46+2 min+2 min
Sun 18 OctZaltbommel 18:40+2 min+3 min
Sat 17 OctZaltbommel 18:380 min—
Fri 16 OctZaltbommel 18:38Partial coverage0 min—
Sun 11 OctZaltbommel 18:370 min—
Sat 10 OctZaltbommel 18:40Partial coverage+2 min+3 min
Fri 9 OctZaltbommel 18:37Partial coverage0 min—
Mon 5 OctCulemborg 18:33Partial coverage0 min—
Sun 4 OctZaltbommel 18:37No data—
Sat 3 OctZaltbommel 18:38No data—
Fri 2 OctZaltbommel 18:37No data—
Sun 27 SeptZaltbommel 18:37No data—
Sat 26 SeptZaltbommel 18:37No data—
Fri 25 SeptHouten 20:330 min—
Sun 20 SeptHouten 00:33−1 min+7 min
Sat 19 SeptZaltbommel 18:37No data—
Fri 18 SeptZaltbommel 18:370 min+1 min
Sun 13 SeptZaltbommel 18:37No data—
Sat 12 SeptUtrecht Leidsche Rijn 17:57No data—
Fri 11 SeptTiel Passewaaij 18:39No data—
Sun 6 SeptZaltbommel 18:40No data—
Sat 5 SeptZaltbommel 18:37No data—