Train NS 7425 Uitgeest – Driebergen-Zeist

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

Running now · updated 07:45

Heading to Driebergen-Zeist No data

Estimated arrival at Driebergen-Zeist 08:38 · 26 km/h

  1. Uitgeest07:03
  2. Zaandijk Zaanse Schans07:19
  3. Amsterdam Centraal07:37
  4. Duivendrecht07:51
  5. Abcoude08:00
  6. Utrecht Centraal08:20
  7. Driebergen-Zeist08:38
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 13 full · 7 partial · 2 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 13 full · 8 partial · 41 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

  • Fri 23 Oct Max en route +7 min · last fix heading to Utrecht Zuilen +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 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, 21 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
07:03on time on time
07:08≈ on time ≈ on time
07:10 / 07:16≈ on time ≈ on time
07:19≈ on time ≈ on time
07:22≈ on time ≈ on time
07:25≈ on time ≈ on time
07:31≈ on time ≈ on time
07:37 / 07:39≈ on time ≈ on time
07:44≈ on time ≈ on time
07:48≈ on time ≈ on time
07:51≈ on time ≈ on time
07:54≈ on time ≈ on time
07:56≈ on time ≈ on time
08:00≈ on time ≈ on time
08:07≈ on time ≈ on time
08:12≈ on time ≈ on time
08:17≈ on time ≈ on time
08:20 / 08:27≈ on time ≈ on time
08:29≈ on time ≈ on time
08:34≈ on time ≈ on time
08:38on 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
Thu 5 NovAmsterdam Muiderpoort 07:44No data—
Wed 4 NovBunnik 08:48Partial coverage0 min—
Tue 3 NovBunnik 08:48Partial coverage0 min—
Mon 2 NovBunnik 08:58No data—
Fri 30 OctBunnik 08:470 min—
Thu 29 OctBunnik 08:49Partial coverage0 min—
Wed 28 OctBunnik 08:49Partial coverage0 min—
Tue 27 OctBunnik 08:48Partial coverage0 min—
Mon 26 OctBunnik 08:480 min—
Fri 23 OctUtrecht Zuilen 08:37+7 min+7 min
Thu 22 OctAmsterdam Sloterdijk 07:460 min—
Wed 21 OctUtrecht Zuilen 08:350 min—
Tue 20 OctUtrecht Zuilen 08:360 min—
Mon 19 OctBunnik 08:460 min—
Fri 16 OctBunnik 08:480 min—
Thu 15 OctBunnik 08:480 min—
Wed 14 OctBunnik 08:480 min—
Tue 13 OctBunnik 08:480 min—
Mon 12 OctBunnik 08:490 min—
Fri 9 OctBunnik 08:470 min—
Thu 8 OctBunnik 08:48Partial coverage0 min—
Wed 7 OctBunnik 08:48Partial coverage0 min—
Tue 6 OctBunnik 08:48Partial coverage0 min—
Mon 5 OctEde-Wageningen 09:14No data—
Fri 2 OctBunnik 08:47No data—
Thu 1 OctBunnik 08:48No data—
Wed 30 SeptBunnik 08:48No data—
Tue 29 SeptBunnik 08:48No data—
Mon 28 SeptBunnik 08:48No data—
Fri 25 SeptBunnik 08:47No data—