Train NS 6042 's-Hertogenbosch – Den Haag Centraal

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

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: Friday 12:29 from 's-Hertogenbosch · Fri 20 Nov

Next departure 12:29 Friday · 's-Hertogenbosch
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 2 full · 6 partial · 2 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 3 full · 11 partial · 22 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 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

  • Sun 18 Oct Max en route +9 min · last fix heading to Utrecht Vaartsche Rijn +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 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=4
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 14 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
12:29on time on time
12:39— —
12:46— —
12:51— —
12:57 / 12:58— —
13:01— —
13:05— —
13:08— —
13:11 / 13:14— —
13:18— —
13:20— —
13:24— —
13:30 / 13:31— —
13:41— —
13:45 / 13:50— —
13:59— —
14:02— —
14:05— —
14:10— —
14:13— —
14:17— —

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 NovVoorburg 14:28Partial coverage0 min—
Sat 14 NovVoorburg 14:28Partial coverage0 min—
Fri 13 NovVoorburg 14:28Partial coverage0 min—
Fri 6 NovVoorburg 14:28No data—
Sun 1 NovVoorburg 14:28Partial coverage0 min—
Sat 31 OctVoorburg 14:28Partial coverage0 min—
Fri 30 OctVoorburg 14:28Partial coverage0 min—
Sun 25 OctVoorburg 14:28No data—
Sat 24 OctVoorburg 14:280 min—
Fri 23 OctVoorburg 14:320 min—
Sun 18 OctUtrecht Vaartsche Rijn 13:30+8 min+9 min
Sat 17 OctVoorburg 14:28Partial coverage0 min—
Fri 16 OctVoorburg 14:27No data—
Sun 11 OctVoorburg 14:30Partial coverage+2 min+4 min
Sat 10 OctVoorburg 14:28Partial coverage0 min—
Fri 9 OctVoorburg 14:27Partial coverage0 min—
Mon 5 OctVoorburg 14:28Partial coverage0 min—
Sun 4 OctVoorburg 14:28No data—
Sat 3 OctVoorburg 14:28No data—
Fri 2 OctVoorburg 14:28No data—
Sun 27 SeptVoorburg 14:28No data—
Sat 26 SeptVoorburg 14:28No data—
Fri 25 SeptVoorburg 14:27No data—
Sun 20 SeptVoorburg 14:28No data—
Sat 19 SeptVoorburg 14:28No data—
Fri 18 SeptVoorburg 14:28No data—
Sun 13 SeptVoorburg 14:28No data—
Sat 12 SeptVoorburg 14:27No data—
Fri 11 SeptVoorburg 14:27No data—
Sun 6 SeptVoorburg 14:29No data—