Train NS 7459 Uitgeest – Driebergen-Zeist

Uitgeest 15:33 → Driebergen-Zeist 17:07 Daily 1 h 34 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 15:33 from Uitgeest · Sat 7 Nov

Next departure 15:33 today · Uitgeest
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 6 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 17 full · 2 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
15:33on time on time
15:38≈ on time ≈ on time
15:41≈ on time ≈ on time
15:44≈ on time ≈ on time
15:47≈ on time ≈ on time
15:50≈ on time ≈ on time
15:56≈ on time ≈ on time
16:02 / 16:04≈ on time ≈ on time
16:10≈ on time ≈ on time
16:13≈ on time ≈ on time
16:16≈ on time ≈ on time
16:19 / 16:27≈ on time ≈ on time
16:30≈ on time ≈ on time
16:33≈ on time ≈ on time
16:41≈ on time ≈ on time
16:46≈ on time ≈ on time
16:51≈ on time ≈ on time
16:54 / 16:56≈ on time ≈ on time
16:58≈ on time ≈ on time
17:03≈ on time ≈ on time
17:07on 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
Fri 6 NovBunnik 17:17Partial coverage0 min—
Thu 5 NovBunnik 17:17No data—
Wed 4 NovBunnik 17:170 min—
Tue 3 NovBunnik 17:17No data—
Mon 2 NovBunnik 17:170 min—
Fri 30 OctBunnik 17:170 min—
Thu 29 OctBunnik 17:170 min—
Wed 28 OctBunnik 17:17No data—
Tue 27 OctBunnik 17:19No data—
Mon 26 OctBunnik 17:170 min—
Fri 23 OctUtrecht Zuilen 17:020 min—
Thu 22 OctAmsterdam Sloterdijk 16:180 min—
Wed 21 OctUtrecht Zuilen 17:060 min—
Tue 20 OctUtrecht Zuilen 17:050 min—
Mon 19 OctBunnik 17:160 min—
Fri 16 OctBunnik 17:240 min—
Thu 15 OctBunnik 17:170 min—
Wed 14 OctBunnik 17:17No data—
Tue 13 OctBunnik 17:17No data—
Mon 12 OctBunnik 17:170 min—
Fri 9 OctBreukelen 17:20Partial coverage0 min—
Thu 8 OctBunnik 17:170 min—
Wed 7 OctBunnik 17:170 min—
Tue 6 OctBunnik 17:180 min—
Mon 5 OctEde-Wageningen 17:430 min—
Fri 2 OctBunnik 17:17No data—
Thu 1 OctBunnik 17:17No data—
Wed 30 SeptBunnik 17:17No data—
Tue 29 SeptBunnik 17:17No data—
Mon 28 SeptBunnik 17:17No data—