Train NS 7463 Uitgeest – Driebergen-Zeist

Uitgeest 16:33 → Driebergen-Zeist 18:08 Daily 1 h 35 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:33 from Uitgeest · Thu 5 Nov

Next departure 16:33 today · Uitgeest
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 9 full · 6 partial · 6 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 44 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 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

  • Wed 7 Oct Max en route +3 min · last fix heading to Bunnik +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
16:33on time on time
16:38≈ on time ≈ on time
16:40 / 16:46≈ on time ≈ on time
16:49≈ on time ≈ on time
16:52≈ on time ≈ on time
16:55≈ on time ≈ on time
17:01≈ on time ≈ on time
17:07 / 17:09≈ on time ≈ on time
17:14≈ on time ≈ on time
17:18≈ on time ≈ on time
17:21≈ on time ≈ on time
17:24≈ on time ≈ on time
17:26≈ on time ≈ on time
17:30≈ on time ≈ on time
17:37≈ on time ≈ on time
17:42≈ on time ≈ on time
17:47≈ on time ≈ on time
17:50 / 17:57≈ on time ≈ on time
17:59≈ on time ≈ on time
18:04≈ on time ≈ on time
18:08on 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
Wed 4 NovBunnik 18:18Partial coverage0 min—
Tue 3 NovBunnik 18:18No data—
Mon 2 NovBunnik 18:18No data—
Fri 30 OctBunnik 18:170 min—
Thu 29 OctUtrecht Vaartsche Rijn 18:13Partial coverage0 min—
Wed 28 OctBunnik 18:18Partial coverage0 min—
Tue 27 OctBunnik 18:18No data—
Mon 26 OctBunnik 18:18Partial coverage0 min—
Fri 23 OctUtrecht Zuilen 18:010 min—
Thu 22 OctAmsterdam Sloterdijk 17:160 min—
Wed 21 OctUtrecht Zuilen 18:110 min—
Tue 20 OctUtrecht Zuilen 18:110 min—
Mon 19 OctBunnik 18:160 min—
Fri 16 OctBunnik 18:190 min—
Thu 15 OctBunnik 18:18No data—
Wed 14 OctBunnik 18:19No data—
Tue 13 OctBunnik 18:18No data—
Mon 12 OctBunnik 18:180 min—
Fri 9 OctBunnik 18:170 min—
Thu 8 OctUtrecht Vaartsche Rijn 18:13Partial coverage0 min—
Wed 7 OctBunnik 18:18Partial coverage+3 min+3 min
Tue 6 OctBunnik 18:18Partial coverage0 min—
Mon 5 OctDriebergen-Zeist 18:400 min—
Fri 2 OctBunnik 18:17No data—
Thu 1 OctBunnik 18:18No data—
Wed 30 SeptBunnik 18:18No data—
Tue 29 SeptBunnik 18:18No data—
Mon 28 SeptBunnik 18:18No data—
Fri 25 SeptBunnik 18:17No data—
Thu 24 SeptUtrecht Centraal 18:12No data—