Train NS 6068 's-Hertogenbosch – Den Haag Centraal

's-Hertogenbosch 18:59 → Den Haag Centraal 20:47 Fri, Sat, Sun 1 h 48 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November +2 min

Next service: today 18:59 from 's-Hertogenbosch · Sun 15 Nov

Next departure 18:59 today · 's-Hertogenbosch
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 5 full · 4 partial · 2 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 11 full · 7 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 23 Oct Max en route +4 min · last fix heading to Houten Castellum +4 min

Distribution · 90 days

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

  • Early 6% · 1
  • On time 89% · 16
  • 3–10 min 6% · 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
  • 86% F n=7
  • 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, 18 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
18:59on time on time
19:09≈ on time ≈ on time
19:16≈ on time ≈ on time
19:21≈ on time ≈ on time
19:27 / 19:28≈ on time ≈ +1 min
19:31≈ on time ≈ +1 min
19:35≈ on time ≈ +1 min
19:38≈ on time ≈ +1 min
19:41 / 19:44≈ on time ≈ +1 min
19:48≈ on time ≈ +1 min
19:50≈ on time ≈ +1 min
19:54≈ on time ≈ +1 min
20:00 / 20:01≈ on time ≈ +1 min
20:11≈ on time ≈ +1 min
20:15 / 20:20≈ on time ≈ +1 min
20:29≈ on time ≈ +2 min
20:32≈ on time ≈ +2 min
20:35≈ on time ≈ +2 min
20:40≈ on time ≈ +2 min
20:43≈ on time ≈ +2 min
20:47on time +2 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
Sat 14 NovVoorburg 20:59Partial coverage+2 min+2 min
Fri 13 Nov— 20:49+1 min+1 min
Fri 6 Nov— 20:49+2 min+2 min
Sun 1 NovVoorburg 20:57Partial coverage0 min—
Sat 31 OctVoorburg 20:58Partial coverage+1 min—
Fri 30 Oct— 20:480 min—
Sun 25 OctVoorburg 20:57No data—
Sat 24 OctVoorburg 20:58No data—
Fri 23 OctHouten Castellum 20:55+4 min+4 min
Sun 18 OctUtrecht Vaartsche Rijn 19:53+1 min—
Sat 17 OctVoorburg 20:58Partial coverage0 min—
Fri 16 OctVleuten 20:48Partial coverage0 min—
Sun 11 OctVoorburg 20:59Partial coverage0 min—
Sat 10 OctVoorburg 20:58Partial coverage0 min—
Fri 9 Oct— 20:480 min—
Mon 5 Oct— 20:480 min—
Sun 4 OctHouten 00:050 min+3 min
Sat 3 OctVoorburg 20:580 min+1 min
Sun 27 SeptVoorburg 20:57No data—
Sat 26 SeptVoorburg 20:58No data—
Sun 20 SeptVoorburg 20:59No data—
Sat 19 SeptVoorburg 21:00No data—
Sun 13 SeptVoorburg 20:58No data—
Sat 12 SeptVoorburg 21:06No data—
Sun 6 SeptVoorburg 21:02No data—
Sat 5 SeptUtrecht Centraal 00:25−1 min—
Sun 30 AugVoorburg 20:58No data—
Sat 29 AugVoorburg 20:57No data—
Fri 28 AugHouten Castellum 21:26−1 min—
Sun 23 AugUtrecht Vaartsche Rijn 19:53No data—