Train NS 3182 Utrecht Centraal – Den Haag Centraal

Utrecht Centraal 23:26 → Den Haag Centraal 00:29 Daily 1 h 03 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November +2 min

Next service: today 23:26 from Utrecht Centraal · Sat 14 Nov

Next departure 23:26 today · Utrecht Centraal
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 2 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=5
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 100% S n=5

Stops and timetable

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

Last 90 days, 22 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
23:26on time on time
23:42 / 23:43≈ on time ≈ on time
23:49 / 23:50≈ on time ≈ on time
23:56 / 23:58≈ on time ≈ on time
00:14 / 00:18≈ on time ≈ on time
00:29on 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 13 Nov— 00:29+2 min+2 min
Wed 11 Nov— 00:290 min—
Sun 8 NovLeiden Centraal 00:340 min—
Sat 7 Nov— 00:290 min+6 min
Wed 4 Nov— 00:290 min—
Sun 1 NovLeiden Centraal 00:330 min—
Sat 31 Oct— 00:300 min—
Wed 28 Oct— 00:310 min—
Mon 26 Oct— 00:310 min—
Sun 25 OctLeiden Centraal 00:330 min—
Fri 23 Oct— 00:530 min+9 min
Thu 22 Oct— 00:370 min—
Wed 21 Oct— 00:33No data—
Tue 20 Oct— 00:300 min—
Mon 19 Oct— 00:310 min—
Sun 18 OctLeiden Centraal 00:320 min—
Sat 17 OctLeiden Centraal 00:32No data—
Wed 14 Oct— 00:410 min—
Tue 13 Oct— 00:310 min—
Sun 11 OctLeiden Centraal 00:320 min—
Sat 10 Oct— 00:430 min—
Fri 9 Oct— 00:300 min+1 min
Thu 8 Oct— 00:310 min—
Wed 7 Oct— 00:300 min—
Sun 4 OctLeiden Centraal 00:34No data—
Sat 3 OctLeiden Centraal 00:32No data—
Sun 27 SeptLeiden Centraal 00:32No data—
Sat 26 SeptAmsterdam Bijlmer ArenA 23:56No data—
Sun 20 SeptLeiden Centraal 00:33No data—
Sun 13 SeptLeiden Centraal 00:33No data—