Train NS 7462 Driebergen-Zeist – Uitgeest

Driebergen-Zeist 18:21 → Uitgeest 19:57 Mon, Tue, Wed, Thu, Fri 1 h 36 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:21 from Driebergen-Zeist · Thu 5 Nov

Next departure 18:21 today · Driebergen-Zeist
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 3 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 23 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 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

  • Wed 7 Oct Max en route +7 min · last fix heading to — +4 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=3
  • 67% W n=3
  • 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, 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
18:21on time on time
18:25≈ on time ≈ on time
18:30≈ on time ≈ on time
18:33 / 18:38≈ on time ≈ on time
18:41≈ on time ≈ on time
18:45≈ on time ≈ on time
18:50≈ on time ≈ on time
18:58≈ on time ≈ on time
19:01≈ on time ≈ on time
19:04 / 19:05≈ on time ≈ on time
19:08≈ on time ≈ on time
19:12≈ on time ≈ on time
19:15≈ on time ≈ on time
19:20 / 19:22≈ on time ≈ on time
19:28≈ on time ≈ on time
19:35≈ on time ≈ on time
19:38≈ on time ≈ on time
19:41≈ on time ≈ on time
19:44 / 19:49≈ on time ≈ on time
19:52≈ on time ≈ on time
19:57on 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 Nov— 19:590 min—
Mon 2 Nov— 20:030 min—
Fri 30 OctBreukelen 19:040 min—
Wed 28 Oct— 19:590 min—
Tue 27 Oct— 19:580 min—
Mon 26 Oct— 19:590 min—
Fri 23 OctAmsterdam Sloterdijk 02:260 min—
Thu 22 Oct— 20:030 min—
Wed 21 OctUtrecht Centraal 19:59No data—
Tue 20 OctMaarssen 19:580 min—
Mon 19 OctUtrecht Zuilen 19:590 min—
Fri 16 OctZaandijk Zaanse Schans 20:040 min—
Thu 15 OctUtrecht Vaartsche Rijn 19:530 min—
Wed 14 OctZaandijk Zaanse Schans 20:00No data—
Tue 13 OctUtrecht Centraal 19:51No data—
Mon 12 OctMaarssen 19:510 min—
Fri 9 OctUtrecht Vaartsche Rijn 19:580 min—
Thu 8 Oct— 02:250 min—
Wed 7 Oct— 20:03+4 min+7 min
Tue 6 Oct— 19:580 min—
Mon 5 OctVeenendaal-De Klomp 19:26+1 min+1 min
Fri 2 OctMaarssen 18:59No data—
Fri 25 SeptUtrecht Vaartsche Rijn 18:47No data—
Fri 18 SeptMaarssen 18:59No data—
Fri 11 SeptBreukelen 19:04No data—
Mon 7 SeptDriebergen-Zeist 18:35No data—
Fri 4 SeptBreukelen 19:04No data—
Fri 28 AugAmsterdam Centraal 19:41No data—
Thu 27 AugMaarssen 18:59No data—
Wed 26 AugDuivendrecht 19:22No data—