Train NS 7423 Uitgeest – Driebergen-Zeist

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

✓ Today’s run finished

Today, last fix heading to Bunnik at 08:18 +1 min

  1. Uitgeest06:33
  2. Zaandijk Zaanse Schans06:49
  3. Amsterdam Centraal07:07
  4. Duivendrecht07:21
  5. Abcoude07:30
  6. Bunnik08:04
  7. Driebergen-Zeist08:08

Next service: tomorrow 06:33 from Uitgeest · Wed 18 Nov

Next departure 06:33 tomorrow · Uitgeest
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 2 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 25 full · 4 partial · 33 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

Worst days

  • Thu 22 Oct Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=6
  • 80% T n=5
  • 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, 29 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
06:33on time on time
06:38≈ on time ≈ on time
06:40 / 06:46≈ on time ≈ on time
06:49≈ on time ≈ on time
06:52≈ on time ≈ on time
06:55≈ on time ≈ on time
07:01≈ on time ≈ on time
07:07 / 07:09≈ on time ≈ on time
07:14≈ on time ≈ on time
07:18≈ on time ≈ on time
07:21≈ on time ≈ on time
07:24≈ on time ≈ on time
07:26≈ on time ≈ on time
07:30≈ on time ≈ on time
07:37≈ on time ≈ on time
07:42≈ on time ≈ on time
07:47≈ on time ≈ on time
07:50 / 07:57≈ on time ≈ on time
07:59≈ on time ≈ on time
08:04≈ on time ≈ on time
08: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
Tue 17 NovBunnik 08:18Partial coverage+1 min+1 min
Mon 16 NovBunnik 08:180 min—
Fri 13 NovBunnik 08:170 min—
Thu 12 NovBunnik 08:180 min—
Wed 11 NovBunnik 08:180 min—
Tue 10 NovBunnik 08:180 min—
Mon 9 NovBunnik 08:180 min—
Fri 6 NovBunnik 08:17No data—
Thu 5 NovBunnik 08:18No data—
Wed 4 NovBunnik 08:180 min—
Tue 3 NovBunnik 08:18Partial coverage0 min—
Mon 2 NovBunnik 08:180 min—
Fri 30 OctBunnik 08:170 min—
Thu 29 OctBunnik 08:200 min—
Wed 28 OctBunnik 08:180 min—
Tue 27 OctBunnik 08:18Partial coverage0 min—
Mon 26 OctBunnik 08:180 min+2 min
Fri 23 OctUtrecht Zuilen 08:050 min—
Thu 22 OctAmsterdam Sloterdijk 07:16+5 min+5 min
Wed 21 OctUtrecht Zuilen 08:120 min—
Tue 20 OctUtrecht Zuilen 08:120 min—
Mon 19 OctBunnik 08:160 min—
Fri 16 OctBunnik 08:170 min—
Thu 15 OctBunnik 08:190 min—
Wed 14 OctBunnik 08:180 min—
Tue 13 OctBunnik 08:180 min—
Mon 12 OctBunnik 08:180 min—
Fri 9 OctBunnik 08:180 min—
Thu 8 OctBunnik 08:180 min—
Wed 7 OctBunnik 08:180 min—