Train NS 7460 Driebergen-Zeist – Uitgeest

Driebergen-Zeist 17:54 → Uitgeest 19:27 Mon, Tue, Wed, Thu, Fri 1 h 33 min · 21 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: tomorrow 17:54 from Driebergen-Zeist · Mon 9 Nov

Next departure 17:54 tomorrow · Driebergen-Zeist
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 12 full · 1 partial · 7 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Uitgeest, 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 23 Oct Max en route +5 min · last fix heading to Krommenie-Assendelft +5 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

  • 100% M n=5
  • 100% T n=2
  • 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, 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
17:54on time on time
17:58≈ on time ≈ on time
18:03≈ on time ≈ on time
18:05 / 18:08≈ on time ≈ on time
18:11≈ on time ≈ on time
18:15≈ on time ≈ on time
18:20≈ on time ≈ on time
18:28≈ on time ≈ +1 min
18:31≈ on time ≈ +1 min
18:34 / 18:40≈ on time ≈ +1 min
18:43≈ on time ≈ +1 min
18:47≈ on time ≈ +1 min
18:50≈ on time ≈ +1 min
18:55 / 18:57≈ on time ≈ +1 min
19:03≈ on time ≈ +1 min
19:10≈ on time ≈ +1 min
19:13≈ on time ≈ +1 min
19:16≈ on time ≈ +1 min
19:19≈ on time ≈ +2 min
19:23≈ on time ≈ +2 min
19:27on time +2 min

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 NovAmsterdam Amstel 19:28Partial coverage0 min—
Thu 5 NovUtrecht Zuilen 19:28No data—
Wed 4 NovMaarssen 19:29No data—
Tue 3 NovUtrecht Zuilen 19:29No data—
Mon 2 NovUtrecht Centraal 19:290 min—
Fri 30 OctAmsterdam Muiderpoort 19:30No data—
Thu 29 OctUtrecht Vaartsche Rijn 19:280 min—
Wed 28 OctUtrecht Zuilen 19:280 min—
Tue 27 OctUtrecht Vaartsche Rijn 19:31No data—
Mon 26 OctUtrecht Centraal 19:370 min—
Fri 23 OctKrommenie-Assendelft 19:36+5 min+5 min
Thu 22 Oct— 19:310 min—
Wed 21 OctAmsterdam Bijlmer ArenA 19:290 min—
Tue 20 OctAmsterdam Bijlmer ArenA 19:280 min—
Mon 19 OctAmsterdam Amstel 19:290 min—
Fri 16 OctZaandijk Zaanse Schans 19:340 min—
Thu 15 OctAbcoude 19:400 min—
Wed 14 OctZaandijk Zaanse Schans 19:30No data—
Tue 13 OctDuivendrecht 19:21No data—
Mon 12 OctAmsterdam Muiderpoort 19:210 min—
Fri 9 OctAmsterdam Holendrecht 19:28Partial coverage0 min—
Thu 8 OctUtrecht Vaartsche Rijn 19:29+1 min+1 min
Wed 7 OctUtrecht Centraal 18:220 min—
Tue 6 OctUtrecht Vaartsche Rijn 19:31+2 min+6 min
Mon 5 OctUtrecht Zuilen 18:570 min—
Fri 2 OctAmsterdam Amstel 19:01No data—
Thu 1 OctUtrecht Vaartsche Rijn 18:15No data—
Wed 30 SeptUtrecht Centraal 18:18No data—
Tue 29 SeptUtrecht Vaartsche Rijn 18:14No data—
Mon 28 SeptUtrecht Vaartsche Rijn 18:14No data—