Train NS 6062 's-Hertogenbosch – Den Haag Centraal

's-Hertogenbosch 17:29 → Den Haag Centraal 19:17 Fri, Sat, Sun 1 h 48 min · 21 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 17:29 from 's-Hertogenbosch · Fri 13 Nov

Next departure 17:29 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 3 full · 4 partial · 3 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 13 full · 8 partial · 15 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 Den Haag Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +3 min · last fix heading to Woerden +3 min

Distribution · 90 days

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

  • Early 24% · 5
  • On time 71% · 15
  • 3–10 min 5% · 1
  • 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
  • 90% F n=10
  • 100% S n=6
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
17:29on time on time
17:39≈ on time ≈ on time
17:46≈ on time ≈ on time
17:51≈ on time ≈ on time
17:57 / 17:58≈ on time ≈ on time
18:01≈ on time ≈ on time
18:05≈ on time ≈ on time
18:08≈ on time ≈ on time
18:11 / 18:14≈ on time ≈ on time
18:18≈ on time ≈ on time
18:20≈ on time ≈ on time
18:24≈ on time ≈ on time
18:30 / 18:31≈ on time ≈ on time
18:41≈ on time ≈ on time
18:45 / 18:50≈ on time ≈ on time
18:59≈ on time ≈ on time
19:02≈ on time ≈ on time
19:05≈ on time ≈ on time
19:10≈ on time ≈ on time
19:13≈ on time ≈ on time
19:17on 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
Fri 6 NovGouda Goverwelle 19:18Partial coverage0 min—
Sun 1 NovVoorburg 19:28Partial coverage0 min—
Sat 31 OctVoorburg 19:27Partial coverage0 min—
Fri 30 OctGouda 19:18No data—
Sun 25 OctVoorburg 19:29No data—
Sat 24 OctVoorburg 19:310 min—
Fri 23 OctVoorburg 19:270 min—
Sun 18 OctUtrecht Vaartsche Rijn 18:220 min+1 min
Sat 17 OctVoorburg 19:28Partial coverage0 min—
Fri 16 OctVoorburg 19:27No data—
Sun 11 OctVoorburg 19:28Partial coverage0 min—
Sat 10 OctVoorburg 19:29Partial coverage0 min—
Fri 9 OctWoerden 19:23Partial coverage+3 min+3 min
Mon 5 OctUtrecht Vaartsche Rijn 19:18Partial coverage0 min—
Sun 4 OctVoorburg 19:30No data—
Sat 3 OctVoorburg 19:27No data—
Fri 2 OctUtrecht Lunetten 21:58−2 min—
Sun 27 SeptVoorburg 19:28No data—
Sat 26 SeptUtrecht Vaartsche Rijn 01:21−1 min+7 min
Fri 25 SeptHouten 18:540 min—
Mon 21 SeptUtrecht Lunetten 22:200 min—
Sun 20 SeptVoorburg 19:28No data—
Sat 19 SeptVoorburg 19:28No data—
Fri 18 SeptGouda Goverwelle 18:55−1 min—
Sun 13 SeptVoorburg 19:28No data—
Sat 12 SeptVoorburg 19:28No data—
Fri 11 SeptGouda 19:04−1 min—
Sun 6 SeptVoorburg 19:28No data—
Sat 5 SeptVoorburg 19:27No data—
Fri 4 SeptUtrecht Lunetten 21:41−3 min+1 min