Train NS 7453 Uitgeest – Driebergen-Zeist

Uitgeest 14:03 → Driebergen-Zeist 15:38 Daily 1 h 35 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:03 from Uitgeest · Fri 6 Nov

Next departure 14:03 today · Uitgeest
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 11 full · 6 partial · 4 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 12 full · 8 partial · 42 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

Worst days

  • Fri 9 Oct Max en route +6 min · last fix heading to Bunnik +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=3
  • 100% T n=4
  • 75% 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, 20 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:03on time on time
14:08≈ on time ≈ on time
14:10 / 14:16≈ on time ≈ on time
14:19≈ on time ≈ on time
14:22≈ on time ≈ on time
14:25≈ on time ≈ on time
14:31≈ on time ≈ on time
14:37 / 14:41≈ on time ≈ on time
14:46≈ on time ≈ on time
14:49≈ on time ≈ on time
14:53≈ on time ≈ on time
14:56≈ on time ≈ on time
14:58≈ on time ≈ on time
15:02≈ on time ≈ on time
15:09≈ on time ≈ on time
15:14≈ on time ≈ on time
15:19≈ on time ≈ on time
15:22 / 15:27≈ on time ≈ on time
15:29≈ on time ≈ on time
15:34≈ on time ≈ on time
15:38on 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
Thu 5 NovBunnik 15:48No data—
Wed 4 NovBunnik 15:49Partial coverage+1 min+1 min
Tue 3 NovBunnik 15:48Partial coverage0 min—
Mon 2 NovBunnik 15:570 min—
Fri 30 OctBunnik 15:490 min—
Thu 29 OctBunnik 15:480 min—
Wed 28 OctBunnik 15:48Partial coverage0 min—
Tue 27 OctBunnik 15:50Partial coverage0 min—
Mon 26 OctBunnik 15:48Partial coverage0 min—
Fri 23 OctUtrecht Zuilen 15:310 min—
Thu 22 OctAmsterdam Sloterdijk 14:570 min—
Wed 21 OctUtrecht Zuilen 15:44No data—
Tue 20 OctUtrecht Zuilen 15:430 min—
Mon 19 OctBunnik 15:460 min—
Fri 16 OctBunnik 15:470 min—
Thu 15 OctBunnik 15:510 min—
Wed 14 OctBunnik 15:48No data—
Tue 13 OctBunnik 15:48No data—
Mon 12 OctBunnik 15:480 min—
Fri 9 OctBunnik 15:53+6 min+6 min
Thu 8 OctBunnik 15:48Partial coverage+1 min+1 min
Wed 7 OctBunnik 15:48Partial coverage0 min—
Tue 6 OctBunnik 15:48Partial coverage0 min—
Mon 5 OctEde-Wageningen 16:130 min—
Fri 2 OctBunnik 15:47No data—
Thu 1 OctBunnik 15:48No data—
Wed 30 SeptBunnik 15:50No data—
Tue 29 SeptBunnik 15:48No data—
Mon 28 SeptBunnik 15:48No data—
Fri 25 SeptBunnik 15:48No data—