Train NS 3110 Utrecht Centraal – Den Haag Centraal

Utrecht Centraal 05:14 → Den Haag Centraal 06:29 Mon, Tue, Wed, Thu, Fri, Sat 1 h 15 min · 6 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 14 November +3 min

Next service: tomorrow 05:14 from Utrecht Centraal · Mon 16 Nov

Full trip card
Next departure 05:14 tomorrow · Utrecht Centraal
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 19 full · 3 partial · 3 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 28 full · 4 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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 24 Oct Max en route +5 min · last fix heading to Leiden Centraal +5 min
  • Sat 14 Nov Max en route +3 min · last fix heading to Leiden Centraal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • 67% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
Utrecht Centraal
05:14on time on time
Amsterdam Bijlmer ArenA
05:30≈ on time ≈ on time
Amsterdam Zuid
05:36 / 05:40≈ on time ≈ +1 min
Schiphol Airport
05:46 / 05:59≈ on time ≈ +1 min
Leiden Centraal
06:16 / 06:18≈ on time ≈ +2 min
Den Haag Centraal
06:29+1 min +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 NovLeiden Centraal 06:32Partial coverage+3 min+3 min
Fri 13 NovLeiden Centraal 06:320 min—
Thu 12 NovLeiden Centraal 06:33+2 min+2 min
Wed 11 NovLeiden Centraal 06:330 min—
Tue 10 NovLeiden Centraal 06:32+1 min+1 min
Mon 9 NovLeiden Centraal 06:320 min—
Sat 7 NovLeiden Centraal 06:33+1 min+1 min
Fri 6 NovLeiden Centraal 06:34No data—
Thu 5 NovLeiden Centraal 06:330 min—
Wed 4 NovLeiden Centraal 06:320 min—
Tue 3 NovLeiden Centraal 06:32+1 min—
Mon 2 NovLeiden Centraal 06:32No data—
Sat 31 OctLeiden Centraal 06:33Partial coverage0 min+1 min
Fri 30 OctLeiden Centraal 06:320 min—
Thu 29 Oct— 06:30No data—
Wed 28 OctLeiden Centraal 06:32+1 min—
Tue 27 OctLeiden Centraal 06:35+2 min+3 min
Mon 26 OctLeiden Centraal 06:34+2 min+2 min
Sat 24 OctLeiden Centraal 06:40Partial coverage+5 min+5 min
Fri 23 OctLeiden Centraal 06:33+1 min+1 min
Thu 22 OctLeiden Centraal 06:320 min—
Wed 21 OctLeiden Centraal 06:320 min—
Tue 20 OctLeiden Centraal 06:320 min—
Mon 19 OctLeiden Centraal 06:320 min—
Sat 17 OctLeiden Centraal 06:32+1 min+1 min
Fri 16 OctLeiden Centraal 06:320 min—
Thu 15 OctLeiden Centraal 06:320 min—
Wed 14 OctLeiden Centraal 06:34+2 min+3 min
Tue 13 OctLeiden Centraal 06:33+1 min—
Mon 12 OctLeiden Centraal 06:34+2 min+3 min