Train NS 3185 Den Haag Centraal – Utrecht Centraal

Den Haag Centraal 22:01 → Utrecht Centraal 23:03 Daily 1 h 02 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +3 min

Next service: today 22:01 from Den Haag Centraal · Thu 5 Nov

Next departure 22:01 today · Den Haag Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 16 full · 2 partial · 8 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 18 full · 2 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Utrecht 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 9 Oct Max en route +11 min · last fix heading to — +10 min
  • Wed 7 Oct Max en route +8 min · last fix heading to — +8 min

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 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 50% W n=2
  • 100% T n=3
  • 67% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
22:01on time on time
22:12 / 22:14≈ on time ≈ +1 min
22:30 / 22:33≈ on time ≈ +2 min
22:39 / 22:41≈ on time ≈ +3 min
22:46 / 22:47≈ on time ≈ +3 min
23:03+1 min +4 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
Wed 4 Nov— 23:09+3 min+3 min
Mon 2 Nov— 23:04+2 min+2 min
Sun 1 NovSittard 00:59Partial coverage0 min—
Sat 31 OctAmsterdam Bijlmer ArenA 23:010 min—
Thu 29 Oct— 23:040 min—
Wed 28 Oct— 23:04No data—
Tue 27 Oct— 23:09No data—
Mon 26 Oct— 23:04No data—
Sun 25 OctAmsterdam Bijlmer ArenA 23:04No data—
Sat 24 OctSchiphol Airport 23:080 min—
Fri 23 Oct— 23:040 min—
Thu 22 Oct— 23:070 min—
Wed 21 Oct— 23:04No data—
Mon 19 Oct— 23:050 min—
Sun 18 OctAmsterdam Bijlmer ArenA 23:05+1 min—
Sat 17 OctDen Haag Centraal 23:070 min—
Fri 16 Oct— 23:05+1 min+1 min
Thu 15 Oct— 23:13No data—
Wed 14 Oct— 23:04No data—
Tue 13 Oct— 23:13No data—
Mon 12 Oct— 23:040 min—
Sun 11 OctSittard 01:04Partial coverage0 min—
Sat 10 OctDen Haag Centraal 23:050 min—
Fri 9 Oct— 23:21+10 min+11 min
Thu 8 Oct— 23:05+1 min+1 min
Wed 7 Oct— 23:21+8 min+8 min
Tue 6 Oct— 23:06+1 min+1 min
Mon 5 Oct— 23:05+1 min+1 min
Sun 4 OctAmsterdam Bijlmer ArenA 23:01No data—
Sat 3 OctAmsterdam Bijlmer ArenA 23:03No data—