Train NS 6059 Den Haag Centraal – 's-Hertogenbosch

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

It does not run today

Last recorded run: Sunday 15 November +2 min

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

Next departure 15:13 Friday · Den Haag Centraal
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 7 full · 3 partial · 1 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 23 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: +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

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

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