Train NS 6074 's-Hertogenbosch – Den Haag Centraal

's-Hertogenbosch 20:29 → Den Haag Centraal 22:15 Daily 1 h 46 min · 21 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 20:29 from 's-Hertogenbosch · Mon 9 Nov

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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 100% F n=4
  • 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, 20 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
20:29on time on time
20:39≈ on time ≈ on time
20:46≈ on time ≈ on time
20:51≈ on time ≈ on time
20:57 / 20:58≈ on time ≈ on time
21:01≈ on time ≈ on time
21:05≈ on time ≈ on time
21:08≈ on time ≈ on time
21:11 / 21:14≈ on time ≈ on time
21:18≈ on time ≈ +1 min
21:20≈ on time ≈ +1 min
21:24≈ on time ≈ +1 min
21:30 / 21:31≈ on time ≈ +1 min
21:41≈ on time ≈ +1 min
21:45 / 21:47≈ on time ≈ +1 min
21:56≈ on time ≈ +1 min
22:00≈ on time ≈ on time
22:02≈ on time ≈ on time
22:07≈ on time ≈ on time
22:10≈ on time ≈ on time
22:15on 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 Nov— 22:140 min—
Thu 5 Nov— 22:14No data—
Wed 4 Nov— 22:140 min—
Tue 3 Nov— 22:14No data—
Sun 1 NovVoorburg 22:24Partial coverage0 min—
Sat 31 OctVoorburg 22:24Partial coverage0 min—
Fri 30 Oct— 22:16No data—
Thu 29 Oct— 21:420 min—
Wed 28 Oct— 22:160 min—
Tue 27 Oct— 22:250 min—
Mon 26 Oct— 22:16No data—
Sun 25 OctVoorburg 22:28No data—
Sat 24 OctVoorburg 22:270 min—
Fri 23 Oct— 21:410 min—
Thu 22 Oct— 22:19No data—
Wed 21 Oct— 22:19No data—
Mon 19 Oct— 21:21No data—
Sun 18 OctUtrecht Vaartsche Rijn 21:23+2 min+3 min
Sat 17 OctVoorburg 22:29Partial coverage0 min—
Fri 16 Oct— 22:160 min+3 min
Thu 15 Oct— 22:16No data—
Wed 14 Oct— 22:18No data—
Tue 13 Oct— 22:19No data—
Mon 12 Oct— 22:210 min—
Sun 11 OctVoorburg 22:25Partial coverage+1 min—
Sat 10 OctZoetermeer 22:17Partial coverage+1 min—
Fri 9 Oct— 22:160 min—
Wed 7 Oct— 22:16+1 min—
Tue 6 Oct— 22:160 min—
Mon 5 Oct— 22:170 min—