Train NS 7427 Uitgeest – Driebergen-Zeist

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

✓ Today’s run finished

Today, last fix heading to Bunnik at 09:17 +2 min

  1. Uitgeest07:33
  2. Zaandijk Zaanse Schans07:49
  3. Amsterdam Centraal08:07
  4. Duivendrecht08:21
  5. Abcoude08:30
  6. Bunnik09:03
  7. Driebergen-Zeist09:07

Next service: tomorrow 07:33 from Uitgeest · Thu 19 Nov

Next departure 07:33 tomorrow · Uitgeest
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 8 full · 10 partial · 4 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 13 full · 13 partial · 37 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: +2 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 12 Nov Max en route +3 min · last fix heading to Bunnik +3 min

Distribution · 90 days

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

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

On-time by weekday

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