Train NS 7455 Uitgeest – Driebergen-Zeist

Uitgeest 14:33 → Driebergen-Zeist 16:08 Mon, Tue, Wed, Thu, Fri 1 h 35 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 14:33 from Uitgeest · Tue 17 Nov

Next departure 14:33 today · Uitgeest
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 5 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 15 full · 10 partial · 38 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

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=4
  • 100% W n=3
  • 100% T n=4
  • 100% F n=5
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

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