Train NS 6038 's-Hertogenbosch – Den Haag Centraal

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: Friday 11:29 from 's-Hertogenbosch · Fri 13 Nov

Next departure 11:29 Friday · 's-Hertogenbosch
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 3 full · 3 partial · 4 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 3 full · 7 partial · 26 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=2
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 10 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
11:29on time on time
11:39— —
11:46— —
11:51— —
11:57 / 11:58— —
12:01— —
12:05— —
12:08— —
12:11 / 12:14— —
12:18— —
12:20— —
12:24— —
12:30 / 12:31— —
12:41— —
12:45 / 12:50— —
12:59— —
13:02— —
13:05— —
13:10— —
13:13— —
13: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
Fri 6 NovVoorburg 13:28No data—
Sun 1 NovVoorburg 13:29Partial coverage0 min—
Sat 31 OctVoorburg 13:28Partial coverage0 min—
Fri 30 OctVoorburg 13:27No data—
Sun 25 OctVoorburg 13:30No data—
Sat 24 OctVoorburg 13:270 min—
Fri 23 OctVoorburg 13:280 min—
Sun 18 OctUtrecht Vaartsche Rijn 12:230 min—
Sat 17 OctVoorburg 13:27Partial coverage0 min—
Fri 16 OctVoorburg 13:29No data—
Sun 11 OctVoorburg 13:28Partial coverage0 min—
Sat 10 OctVoorburg 13:28Partial coverage0 min—
Fri 9 OctVoorburg 13:27Partial coverage0 min—
Mon 5 OctVoorburg 13:28Partial coverage0 min—
Sun 4 OctVoorburg 13:28No data—
Sat 3 OctVoorburg 13:28No data—
Fri 2 OctVoorburg 13:28No data—
Sun 27 SeptVoorburg 13:27No data—
Sat 26 SeptVoorburg 13:28No data—
Fri 25 SeptVoorburg 13:27No data—
Sun 20 SeptVoorburg 13:28No data—
Sat 19 SeptVoorburg 13:29No data—
Fri 18 SeptVoorburg 13:29No data—
Sun 13 SeptVoorburg 13:27No data—
Sat 12 SeptVoorburg 13:31No data—
Fri 11 SeptVoorburg 13:28No data—
Sun 6 SeptVoorburg 13:28No data—
Sat 5 SeptVoorburg 13:28No data—
Fri 4 SeptVoorburg 13:28No data—
Sun 30 AugVoorburg 13:28No data—