Train NS 6072 's-Hertogenbosch – Den Haag Centraal

's-Hertogenbosch 19:59 → Den Haag Centraal 21:47 Daily 1 h 48 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 19:59 from 's-Hertogenbosch · Sat 14 Nov

Next departure 19:59 today · 's-Hertogenbosch
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 16 full · 2 partial · 6 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 26 full · 4 partial · 19 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: +1 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

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=2
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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
19:59on time on time
20:09≈ on time ≈ on time
20:16≈ on time ≈ on time
20:21≈ on time ≈ on time
20:27 / 20:28≈ on time ≈ on time
20:31≈ on time ≈ on time
20:35≈ on time ≈ on time
20:38≈ on time ≈ on time
20:41 / 20:44≈ on time ≈ on time
20:48≈ on time ≈ on time
20:50≈ on time ≈ on time
20:54≈ on time ≈ on time
21:00 / 21:01≈ on time ≈ on time
21:11≈ on time ≈ on time
21:15 / 21:20≈ on time ≈ on time
21:29≈ on time ≈ +1 min
21:32≈ on time ≈ +1 min
21:35≈ on time ≈ +1 min
21:40≈ on time ≈ +1 min
21:43≈ on time ≈ +1 min
21:47on 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 13 Nov— 21:490 min+2 min
Thu 12 Nov— 21:52+1 min+1 min
Wed 11 Nov— 21:480 min—
Tue 10 Nov— 21:490 min—
Mon 9 Nov— 21:480 min—
Fri 6 Nov— 21:49+1 min—
Thu 5 Nov— 21:490 min—
Wed 4 Nov— 21:490 min—
Mon 2 Nov— 21:52+2 min+2 min
Sun 1 NovVoorburg 21:580 min—
Sat 31 OctVoorburg 21:58Partial coverage0 min—
Thu 29 Oct— 21:120 min—
Wed 28 Oct— 21:49No data—
Tue 27 Oct— 21:490 min—
Mon 26 Oct— 21:480 min—
Sun 25 OctVoorburg 21:58No data—
Sat 24 OctVoorburg 21:57No data—
Fri 23 Oct— 21:490 min—
Thu 22 Oct— 21:59No data—
Wed 21 Oct— 21:48No data—
Mon 19 Oct— 20:45No data—
Sun 18 OctUtrecht Vaartsche Rijn 20:520 min—
Sat 17 OctVoorburg 21:58Partial coverage0 min—
Fri 16 Oct— 21:480 min—
Thu 15 Oct— 21:50No data—
Wed 14 Oct— 21:48No data—
Tue 13 Oct— 21:550 min—
Mon 12 Oct— 21:480 min—
Sun 11 OctVoorburg 21:59Partial coverage+2 min+3 min
Sat 10 OctVoorburg 21:57Partial coverage0 min—