Train NS 6010 Utrecht Centraal – Den Haag Centraal

Utrecht Centraal 05:12 → Den Haag Centraal 06:17 Mon, Tue, Wed, Thu, Fri 1 h 05 min · 13 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: Monday 05:12 from Utrecht Centraal · Mon 16 Nov

Next departure 05:12 Monday · Utrecht Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 16 full · 4 partial · 1 no data
On-time · 90 days
97%
62/64 runs under 3 min
RT coverage: 59 full · 5 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 29 Aug Max en route +53 min · last fix heading to Zoetermeer +53 min
  • Tue 10 Nov Max en route +7 min · last fix heading to Voorburg +6 min

Distribution · 90 days

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

  • Early 33% · 21
  • On time 64% · 41
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=13
  • 92% T n=13
  • 100% W n=12
  • 100% T n=13
  • 100% F n=12
  • 0% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 64 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
05:12on time on time
05:17≈ on time ≈ on time
05:19≈ on time ≈ on time
05:22≈ on time ≈ on time
05:28≈ on time ≈ +1 min
05:37≈ on time ≈ +1 min
05:41 / 05:50≈ on time ≈ +1 min
05:59≈ on time ≈ +1 min
06:02≈ on time ≈ +1 min
06:05≈ on time ≈ +1 min
06:10≈ on time ≈ +2 min
06:13≈ on time ≈ +2 min
06:17on 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
Fri 13 NovVoorburg 06:28Partial coverage0 min—
Thu 12 NovVoorburg 06:280 min—
Wed 11 NovVoorburg 06:280 min—
Tue 10 NovVoorburg 06:34+6 min+7 min
Mon 9 NovVoorburg 06:280 min—
Fri 6 NovVoorburg 06:28No data—
Thu 5 NovVoorburg 06:280 min—
Wed 4 NovVoorburg 06:280 min—
Tue 3 NovVoorburg 06:280 min—
Mon 2 NovVoorburg 06:280 min—
Fri 30 OctVoorburg 06:28Partial coverage0 min—
Thu 29 OctVoorburg 06:280 min—
Wed 28 OctVoorburg 06:280 min—
Tue 27 OctVoorburg 06:28+1 min+1 min
Mon 26 OctVoorburg 06:280 min—
Fri 23 OctVoorburg 06:28Partial coverage0 min—
Thu 22 OctVoorburg 06:280 min—
Wed 21 OctVoorburg 06:280 min—
Tue 20 OctVoorburg 06:30+2 min+2 min
Mon 19 OctVoorburg 06:29+2 min+4 min
Fri 16 OctVoorburg 06:28Partial coverage0 min—
Thu 15 OctVoorburg 06:280 min—
Wed 14 OctVoorburg 06:280 min—
Tue 13 OctVoorburg 06:31+3 min+3 min
Mon 12 OctVoorburg 06:28+1 min+1 min
Fri 9 OctVoorburg 06:27Partial coverage0 min—
Thu 8 OctVoorburg 06:31+2 min+2 min
Wed 7 OctVoorburg 06:280 min—
Tue 6 OctVoorburg 06:280 min—
Mon 5 OctUtrecht Centraal 12:200 min+2 min