Train NS 6091 Den Haag Centraal – Utrecht Centraal

Den Haag Centraal 23:16 → Utrecht Centraal 00:14 Daily 0 h 58 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 23:16 from Den Haag Centraal · Sat 14 Nov

Next departure 23:16 today · Den Haag Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 4 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 15 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 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

  • Tue 10 Nov Max en route +14 min · last fix heading to — +14 min
  • Mon 12 Oct Max en route +10 min · last fix heading to — +7 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 93% · 28
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 83% T n=6
  • 100% W n=4
  • 100% T n=4
  • 100% F n=6
  • 100% S n=2
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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:16on time on time
23:20≈ on time ≈ on time
23:23≈ on time ≈ on time
23:28≈ on time ≈ on time
23:31≈ on time ≈ on time
23:33≈ on time ≈ on time
23:43 / 23:45≈ on time ≈ on time
23:48≈ on time ≈ on time
23:57 / 23:58≈ on time ≈ on time
00:04≈ on time ≈ on time
00:07≈ on time ≈ on time
00:10≈ on time ≈ on time
00:14on 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:150 min—
Thu 12 Nov— 01:040 min—
Wed 11 Nov— 01:030 min—
Tue 10 Nov— 01:29+14 min+14 min
Mon 9 Nov— 01:030 min—
Fri 6 Nov— 00:140 min—
Thu 5 Nov— 01:03No data—
Wed 4 Nov— 01:040 min—
Tue 3 Nov— 01:030 min—
Mon 2 Nov— 00:140 min—
Sun 1 NovZaltbommel 01:090 min—
Sat 31 OctVoorburg 00:190 min—
Fri 30 Oct— 00:150 min—
Thu 29 Oct— 23:440 min—
Wed 28 Oct— 01:030 min—
Tue 27 Oct— 01:030 min—
Mon 26 Oct— 01:030 min—
Sun 25 OctZaltbommel 01:070 min—
Sat 24 Oct— 00:18No data—
Fri 23 Oct— 00:160 min—
Thu 22 Oct— 01:120 min—
Wed 21 Oct— 01:03No data—
Tue 20 Oct— 01:030 min—
Sat 17 OctUtrecht Leidsche Rijn 00:24No data—
Fri 16 Oct— 00:150 min—
Thu 15 Oct— 01:05No data—
Wed 14 Oct— 01:03No data—
Tue 13 Oct— 01:040 min—
Mon 12 Oct— 01:16+7 min+10 min
Sun 11 OctZaltbommel 01:080 min—