Train NS 7429 Uitgeest → Driebergen-Zeist

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

NS 7429 Uitgeest–Driebergen-Zeist: final delay under 3 min on 13 of its 14 runs with data in the last 30 days (93%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:06 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 08:03 from Uitgeest · Mon 23 Nov

Next departure 08:03 tomorrow · Uitgeest
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 11 full · 3 partial · 6 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 20 full · 4 partial · 39 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: +1 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 +4 min · last fix heading to Bunnik +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=5
  • 80% T n=5
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
08:03on time on time
08:08≈ on time ≈ on time
08:11≈ on time ≈ on time
08:14≈ on time ≈ on time
08:17≈ on time ≈ on time
08:20≈ on time ≈ on time
08:26≈ on time ≈ on time
08:32 / 08:34≈ on time ≈ on time
08:40≈ on time ≈ on time
08:43≈ on time ≈ on time
08:47≈ on time ≈ on time
08:50 / 08:57≈ on time ≈ +1 min
09:00≈ on time ≈ +1 min
09:03≈ on time ≈ +1 min
09:11≈ on time ≈ +1 min
09:16≈ on time ≈ +1 min
09:21≈ on time ≈ +1 min
09:24 / 09:26≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:33≈ on time ≈ +1 min
09:37on 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 NovBunnik 09:47Partial coverage0 min—
Thu 19 NovBunnik 09:480 min—
Wed 18 NovBunnik 09:480 min—
Tue 17 NovBunnik 09:480 min—
Mon 16 NovBunnik 09:49+1 min+1 min
Fri 13 NovBunnik 09:47Partial coverage0 min—
Thu 12 NovBunnik 09:52+4 min+4 min
Wed 11 NovBunnik 09:480 min—
Tue 10 NovBunnik 09:480 min—
Mon 9 NovBunnik 09:49+1 min+1 min
Fri 6 NovBunnik 09:49No data—
Thu 5 NovBunnik 09:54No data—
Wed 4 NovBunnik 09:480 min—
Tue 3 NovBunnik 09:48No data—
Mon 2 NovBunnik 09:53No data—
Fri 30 OctBunnik 09:47Partial coverage0 min—
Thu 29 OctBunnik 09:510 min—
Wed 28 OctBunnik 09:48No data—
Tue 27 OctBunnik 09:48No data—
Mon 26 OctBreukelen 09:210 min—
Fri 23 OctUtrecht Zuilen 09:390 min—
Thu 22 OctAmsterdam Sloterdijk 08:490 min—
Wed 21 OctUtrecht Zuilen 09:43No data—
Tue 20 OctUtrecht Zuilen 09:430 min—
Mon 19 OctBunnik 09:470 min—
Fri 16 OctBunnik 09:470 min—
Thu 15 OctUtrecht Vaartsche Rijn 10:58No data—
Wed 14 OctBunnik 09:480 min—
Tue 13 OctBunnik 09:48No data—
Mon 12 OctBunnik 09:49No data—