Train NS 3189 Den Haag Centraal – Utrecht Centraal

Den Haag Centraal 23:01 → Utrecht Centraal 00:05 Daily 1 h 04 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 23:01 from Den Haag Centraal · Fri 6 Nov

Next departure 23:01 today · Den Haag Centraal
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sun 1 Nov Max en route +17 min · last fix heading to 's-Hertogenbosch +15 min
  • Tue 6 Oct Max en route +10 min · last fix heading to — +10 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Amsterdam Bijlmer ArenA +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 27
  • 3–10 min 3% · 1
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 67% T n=3
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 30 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:01on time on time
23:12 / 23:14≈ on time ≈ +1 min
23:30 / 23:33≈ on time ≈ +1 min
23:39 / 23:42≈ on time ≈ +1 min
23:46 / 23:47≈ on time ≈ +1 min
00:05on time +1 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
Thu 5 Nov— 00:070 min—
Wed 4 Nov— 00:040 min—
Tue 3 Nov— 00:050 min—
Mon 2 Nov— 00:040 min—
Sun 1 Nov's-Hertogenbosch 01:29+15 min+17 min
Sat 31 OctLeiden Centraal 00:060 min—
Fri 30 Oct— 00:050 min—
Thu 29 Oct— 00:090 min+2 min
Wed 28 Oct— 23:530 min—
Tue 27 Oct— 00:040 min—
Mon 26 Oct— 00:050 min—
Sun 25 OctAmsterdam Bijlmer ArenA 00:040 min—
Sat 24 Oct— 00:070 min—
Fri 23 Oct— 00:190 min+6 min
Thu 22 Oct— 00:060 min—
Wed 21 Oct— 00:050 min—
Mon 19 Oct— 00:110 min+1 min
Sun 18 OctAmsterdam Bijlmer ArenA 00:010 min—
Sat 17 OctAmsterdam Bijlmer ArenA 00:040 min—
Fri 16 Oct— 00:150 min+6 min
Thu 15 Oct— 00:080 min—
Wed 14 Oct— 00:040 min—
Tue 13 Oct— 00:09No data—
Mon 12 Oct— 00:07+1 min—
Sun 11 Oct's-Hertogenbosch 01:050 min—
Sat 10 Oct— 00:060 min+2 min
Fri 9 Oct— 23:130 min—
Thu 8 Oct— 00:060 min—
Wed 7 Oct— 00:120 min+4 min
Tue 6 Oct— 00:04+10 min+10 min