Train NS 7419 Amsterdam Centraal – Driebergen-Zeist

Amsterdam Centraal 06:04 → Driebergen-Zeist 07:07 Mon, Tue, Wed, Thu, Fri 1 h 03 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 06:04 from Amsterdam Centraal · Thu 5 Nov

Next departure 06:04 today · Amsterdam Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 19 full · 1 partial · 1 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 40 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

  • Wed 28 Oct Max en route +9 min · last fix heading to Bunnik +7 min
  • Tue 20 Oct Max en route +4 min · last fix heading to Utrecht Zuilen +4 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 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 80% W n=5
  • 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 (14 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 10
06:04on time on time
06:09≈ on time ≈ on time
06:12≈ on time ≈ on time
06:16≈ on time ≈ on time
06:19 / 06:27≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06:33≈ on time ≈ +1 min
06:41≈ on time ≈ +1 min
06:46≈ on time ≈ +2 min
06:51≈ on time ≈ +2 min
06:54 / 06:56≈ on time ≈ +2 min
06:58≈ on time ≈ +2 min
07:03≈ on time ≈ +2 min
07:07on time +2 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 4 NovBunnik 07:17Partial coverage0 min+1 min
Tue 3 NovBunnik 07:170 min—
Mon 2 NovBunnik 07:180 min—
Fri 30 OctBunnik 07:170 min—
Thu 29 OctBunnik 07:19+2 min+2 min
Wed 28 OctBunnik 07:25+7 min+9 min
Tue 27 OctBunnik 07:170 min—
Mon 26 OctBunnik 07:170 min—
Fri 23 OctUtrecht Zuilen 07:07+1 min+1 min
Thu 22 Oct— 06:54No data—
Wed 21 OctUtrecht Zuilen 07:06+1 min—
Tue 20 OctUtrecht Zuilen 07:10+4 min+4 min
Mon 19 OctBunnik 07:180 min—
Fri 16 OctBunnik 07:170 min—
Thu 15 OctBunnik 07:17+1 min+1 min
Wed 14 OctBunnik 07:170 min+1 min
Tue 13 OctBunnik 07:170 min—
Mon 12 OctBunnik 07:170 min—
Fri 9 OctBunnik 07:170 min—
Thu 8 OctBunnik 07:18+1 min+1 min
Wed 7 OctBunnik 07:170 min—
Tue 6 OctBunnik 07:18+1 min—
Mon 5 OctEde-Wageningen 07:44No data—
Fri 2 OctBunnik 07:19No data—
Thu 1 OctBunnik 07:17No data—
Wed 30 SeptBunnik 07:17No data—
Tue 29 SeptBunnik 07:17No data—
Mon 28 SeptBunnik 07:17No data—
Fri 25 SeptBunnik 07:19No data—
Thu 24 SeptBunnik 07:18No data—