Train NS 6051 Den Haag Centraal – 's-Hertogenbosch

Den Haag Centraal 13:13 → 's-Hertogenbosch 15:02 Fri, Sat, Sun 1 h 49 min · 21 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

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

Next departure 13:13 Friday · Den Haag Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 4 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 17 full · 7 partial · 15 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: 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

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

  • Early 17% · 4
  • On time 83% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=9
  • 100% S n=8
  • 100% S n=5

Stops and timetable

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

Last 90 days, 24 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
13:13on time on time
13:17≈ on time ≈ on time
13:20≈ on time ≈ on time
13:25≈ on time ≈ on time
13:27≈ on time ≈ on time
13:30≈ on time ≈ on time
13:40 / 13:45≈ on time ≈ on time
13:48≈ on time ≈ on time
13:57 / 13:58≈ on time ≈ +1 min
14:04≈ on time ≈ +1 min
14:07≈ on time ≈ +1 min
14:10≈ on time ≈ +1 min
14:14 / 14:20≈ on time ≈ +1 min
14:22≈ on time ≈ +1 min
14:25≈ on time ≈ +1 min
14:28 / 14:29≈ on time ≈ +1 min
14:32≈ on time ≈ +1 min
14:38≈ on time ≈ +1 min
14:45 / 14:47≈ on time ≈ +1 min
14:53≈ on time ≈ +1 min
15:02on 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 15:07No data—
Sun 1 NovZaltbommel 15:08Partial coverage0 min—
Sat 31 OctCulemborg 15:57Partial coverage0 min+27 min
Fri 30 OctZaltbommel 15:07No data—
Sun 25 OctZaltbommel 15:07No data—
Sat 24 OctTiel Passewaaij 15:160 min—
Fri 23 OctTiel Passewaaij 15:17No data—
Sun 18 OctZaltbommel 15:070 min—
Sat 17 OctZaltbommel 15:070 min—
Fri 16 OctZaltbommel 15:07Partial coverage0 min—
Sun 11 OctZaltbommel 15:07Partial coverage0 min—
Sat 10 OctZaltbommel 15:07Partial coverage0 min—
Fri 9 OctZaltbommel 15:07Partial coverage0 min—
Mon 5 OctZaltbommel 15:07Partial coverage0 min—
Sun 4 OctUtrecht Centraal 00:24−1 min—
Sat 3 OctUtrecht Centraal 17:55−1 min+2 min
Fri 2 OctHouten 00:000 min+3 min
Sun 27 SeptZaltbommel 15:07No data—
Sat 26 SeptHouten 18:53−2 min—
Fri 25 SeptUtrecht Vaartsche Rijn 01:19−3 min+5 min
Mon 21 SeptUtrecht Centraal 21:25+1 min+3 min
Sun 20 SeptUtrecht Vaartsche Rijn 01:20−3 min+6 min
Sat 19 SeptZaltbommel 15:08No data—
Fri 18 SeptHouten 00:07+1 min+2 min
Sun 13 SeptZaltbommel 15:07No data—
Sat 12 SeptUtrecht Vaartsche Rijn 01:04+1 min—
Fri 11 SeptUtrecht Vaartsche Rijn 00:47−1 min+2 min
Sun 6 SeptZaltbommel 15:07No data—
Sat 5 SeptZaltbommel 15:07No data—
Fri 4 SeptZaltbommel 15:07No data—