Train NS 6920 Utrecht Centraal – Den Haag Centraal

Utrecht Centraal 07:44 → Den Haag Centraal 08:47 Mon, Tue, Wed, Thu, Sat, Sun 1 h 03 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Voorburg at 08:58 0 min

  1. Utrecht Centraal07:44
  2. Utrecht Terwijde07:50
  3. Woerden08:00
  4. Gouda08:15
  5. Zoetermeer Oost08:33
  6. Voorburg08:43
  7. Den Haag Centraal08:47

Next service: tomorrow 07:44 from Utrecht Centraal · Mon 9 Nov

Next departure 07:44 tomorrow · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 17 full · 1 partial · 0 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 27 full · 1 partial · 23 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 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=6
  • 100% T n=6
  • — F n=0
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 28 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
07:44on time on time
07:48≈ on time ≈ on time
07:50≈ on time ≈ on time
07:54≈ on time ≈ on time
08:00 / 08:01≈ on time ≈ on time
08:11≈ on time ≈ +1 min
08:15 / 08:20≈ on time ≈ +1 min
08:29≈ on time ≈ +1 min
08:33≈ on time ≈ +1 min
08:35≈ on time ≈ +1 min
08:40≈ on time ≈ +1 min
08:43≈ on time ≈ +1 min
08:47on 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
Sun 8 NovVoorburg 08:58Partial coverage0 min+3 min
Sat 7 NovVoorburg 08:580 min—
Thu 5 NovVoorburg 08:580 min—
Wed 4 NovVoorburg 08:570 min—
Tue 3 NovVoorburg 09:290 min—
Mon 2 NovVoorburg 08:580 min—
Thu 29 OctVoorburg 08:580 min—
Wed 28 OctVoorburg 09:010 min—
Tue 27 OctVoorburg 09:000 min—
Mon 26 OctVoorburg 08:570 min—
Thu 22 OctVoorburg 09:010 min—
Wed 21 OctVoorburg 09:000 min—
Tue 20 OctVoorburg 09:060 min—
Mon 19 OctUtrecht Vaartsche Rijn 07:550 min—
Thu 15 OctVoorburg 08:590 min—
Wed 14 OctVoorburg 08:570 min—
Tue 13 OctVoorburg 09:400 min—
Mon 12 OctVoorburg 08:590 min—
Thu 8 OctVoorburg 08:59+2 min+2 min
Wed 7 OctVoorburg 08:570 min—
Tue 6 OctVoorburg 09:00+2 min+2 min
Thu 1 OctVoorburg 08:59No data—
Wed 30 SeptVoorburg 08:57No data—
Tue 29 SeptVoorburg 08:58No data—
Mon 28 SeptVoorburg 08:58No data—
Thu 24 SeptVoorburg 08:59No data—
Wed 23 SeptVoorburg 08:57No data—
Tue 22 SeptVoorburg 08:58No data—
Mon 21 SeptVoorburg 08:59No data—
Thu 17 SeptVoorburg 08:58No data—