Train NS 7464 Driebergen-Zeist – Uitgeest

Driebergen-Zeist 18:54 → Uitgeest 20:28 Mon, Tue, Wed, Thu, Fri 1 h 34 min · 21 stops NS (Nederlandse Spoorwegen)

Running now · updated 18:54

Heading to Uitgeest 0 min

Estimated arrival at Uitgeest 20:28 · 0 km/h

  1. Driebergen-Zeist18:54
  2. Utrecht Centraal19:05
  3. Abcoude19:28
  4. Duivendrecht19:43
  5. Amsterdam Centraal19:56
  6. Zaandijk Zaanse Schans20:16
  7. Uitgeest20:28

Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 18 runs arrived on time.

On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 17 full · 1 partial · 3 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 26 full · 1 partial · 8 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: +2 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

  • Thu 19 Nov Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=3
  • 100% W n=5
  • 80% T n=5
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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 10Today
18:54on time on time
18:58≈ on time ≈ on time
19:03≈ on time ≈ on time
19:05 / 19:08≈ on time ≈ on time
19:11≈ on time ≈ on time
19:15≈ on time ≈ on time
19:20≈ on time ≈ on time
19:28≈ on time ≈ on time
19:31≈ on time ≈ on time
19:34 / 19:41≈ on time ≈ +1 min
19:43≈ on time ≈ +1 min
19:47≈ on time ≈ +1 min
19:51≈ on time ≈ +1 min
19:56 / 19:57≈ on time ≈ +1 min
20:03≈ on time ≈ +1 min
20:10≈ on time ≈ +1 min
20:13≈ on time ≈ +1 min
20:16≈ on time ≈ +1 min
20:19≈ on time ≈ +1 min
20:23≈ on time ≈ +1 min
20:28on time +1 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 20 NovDriebergen-Zeist 18:50Partial coverage0 min—
Thu 19 Nov— 20:43+8 min+8 min
Wed 18 Nov— 20:29+1 min+2 min
Tue 17 Nov— 20:29+1 min+1 min
Mon 16 Nov— 20:290 min—
Fri 13 NovDriebergen-Zeist 20:290 min—
Thu 12 Nov— 20:29+1 min—
Wed 11 Nov— 20:29+1 min+1 min
Tue 10 Nov— 20:290 min—
Mon 9 Nov— 20:280 min—
Fri 6 Nov— 20:30+1 min—
Thu 5 Nov— 20:29No data—
Wed 4 Nov— 20:29+2 min+2 min
Mon 2 Nov— 20:280 min—
Fri 30 OctDriebergen-Zeist 20:300 min—
Thu 29 Oct— 20:280 min—
Wed 28 Oct— 20:29No data—
Tue 27 Oct— 20:29No data—
Mon 26 Oct— 03:250 min—
Fri 23 OctAbcoude 20:280 min—
Thu 22 Oct— 21:030 min—
Wed 21 Oct— 20:290 min—
Mon 19 Oct— 20:280 min—
Fri 16 OctAmsterdam Muiderpoort 20:290 min—
Thu 15 Oct— 20:23No data—
Wed 14 OctAmsterdam Amstel 20:31No data—
Tue 13 Oct— 20:23No data—
Mon 12 Oct— 20:210 min—
Fri 9 Oct— 20:290 min—
Thu 8 Oct— 03:250 min+3 min