Train NS 7417 Utrecht Centraal – Driebergen-Zeist

Utrecht Centraal 06:26 → Driebergen-Zeist 06:37 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Bunnik at 06:49 +2 min

  1. Utrecht Centraal06:26
  2. Utrecht Vaartsche Rijn06:28
  3. Bunnik06:33
  4. Driebergen-Zeist06:37

Next service: tomorrow 06:26 from Utrecht Centraal · Tue 10 Nov

Next departure 06:26 tomorrow · Utrecht Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 3 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 0 full · 18 partial · 40 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Mon 12 Oct Max en route +4 min · last fix heading to Bunnik +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 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, 18 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
06:26on time on time
06:28— —
06:33— —
06:37— —

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
Mon 9 NovBunnik 06:49Partial coverage+2 min+2 min
Fri 6 NovBunnik 06:47No data—
Thu 5 NovBunnik 06:48No data—
Wed 4 NovBunnik 06:48Partial coverage+2 min+2 min
Tue 3 NovBunnik 06:47Partial coverage0 min—
Mon 2 NovBunnik 06:47No data—
Fri 30 OctBunnik 06:47Partial coverage0 min—
Thu 29 OctBunnik 06:49Partial coverage+2 min+2 min
Wed 28 OctBunnik 06:47Partial coverage0 min—
Tue 27 OctBunnik 06:49Partial coverage+2 min+3 min
Mon 26 OctBunnik 06:49Partial coverage+3 min+3 min
Mon 19 OctBunnik 06:47Partial coverage0 min—
Fri 16 OctBunnik 06:47Partial coverage0 min—
Thu 15 OctBunnik 06:49Partial coverage+2 min+2 min
Wed 14 OctBunnik 06:47Partial coverage0 min—
Tue 13 OctBunnik 06:48Partial coverage+1 min—
Mon 12 OctBunnik 06:51Partial coverage+4 min+4 min
Fri 9 OctBunnik 06:47Partial coverage0 min—
Thu 8 OctBunnik 06:48Partial coverage+1 min+1 min
Wed 7 OctBunnik 06:47Partial coverage0 min—
Tue 6 OctBunnik 06:47Partial coverage+1 min+1 min
Mon 5 OctBunnik 06:48No data—
Fri 2 OctBunnik 06:48No data—
Thu 1 OctBunnik 06:47No data—
Wed 30 SeptBunnik 06:47No data—
Tue 29 SeptBunnik 06:47No data—
Mon 28 SeptBunnik 06:47No data—
Fri 25 SeptBunnik 06:47No data—
Thu 24 SeptBunnik 06:48No data—
Wed 23 SeptBunnik 06:47No data—