Train NS 7451 Utrecht Centraal – Driebergen-Zeist

Utrecht Centraal 14:56 → Driebergen-Zeist 15:07 Daily 0 h 11 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:56 from Utrecht Centraal · Fri 6 Nov

Next departure 14:56 today · Utrecht Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 8 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 46 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: +1 min

Last 30 days

Arrival delay at Driebergen-Zeist, 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=2
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 12 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
14:56on time on time
14:58— —
15:03— —
15:07— —

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 NovBunnik 15:17No data—
Wed 4 NovBunnik 15:18Partial coverage+1 min+1 min
Tue 3 NovBunnik 15:17No data—
Mon 2 NovBunnik 15:17No data—
Fri 30 OctBunnik 15:18Partial coverage0 min—
Thu 29 OctBunnik 15:23Partial coverage0 min—
Wed 28 OctBunnik 15:17No data—
Tue 27 OctBunnik 15:21No data—
Mon 26 OctBunnik 15:19Partial coverage0 min—
Mon 19 OctBunnik 15:180 min—
Fri 16 OctBunnik 15:190 min—
Thu 15 OctBunnik 15:17No data—
Wed 14 OctBunnik 15:18No data—
Tue 13 OctBunnik 15:17No data—
Mon 12 OctBunnik 15:170 min—
Fri 9 OctBunnik 15:18Partial coverage+1 min—
Thu 8 OctBunnik 15:17Partial coverage0 min—
Wed 7 OctBunnik 15:23Partial coverage0 min—
Tue 6 OctBunnik 15:17Partial coverage0 min—
Mon 5 OctEde-Wageningen 15:430 min—
Fri 2 OctBunnik 15:20No data—
Thu 1 OctBunnik 15:17No data—
Wed 30 SeptBunnik 15:17No data—
Tue 29 SeptBunnik 15:18No data—
Mon 28 SeptBunnik 15:17No data—
Fri 25 SeptBunnik 15:19No data—
Thu 24 SeptBunnik 15:17No data—
Wed 23 SeptBunnik 15:18No data—
Tue 22 SeptBunnik 15:17No data—
Mon 21 SeptBunnik 15:17No data—