Train NS 7457 Uitgeest – Driebergen-Zeist

Uitgeest 15:03 → Driebergen-Zeist 16:38 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 16:49 +2 min

  1. Uitgeest15:03
  2. Zaandijk Zaanse Schans15:19
  3. Amsterdam Centraal15:37
  4. Duivendrecht15:51
  5. Abcoude16:00
  6. Bunnik16:34
  7. Driebergen-Zeist16:38

Next service: tomorrow 15:03 from Uitgeest · Wed 18 Nov

Next departure 15:03 tomorrow · Uitgeest
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 10 full · 11 partial · 3 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 14 full · 14 partial · 36 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 28 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
15:03on time on time
15:08≈ on time ≈ on time
15:10 / 15:16≈ on time ≈ on time
15:19≈ on time ≈ on time
15:22≈ on time ≈ on time
15:25≈ on time ≈ on time
15:31≈ on time ≈ on time
15:37 / 15:39≈ on time ≈ on time
15:44≈ on time ≈ on time
15:48≈ on time ≈ on time
15:51≈ on time ≈ on time
15:54≈ on time ≈ on time
15:56≈ on time ≈ on time
16:00≈ on time ≈ on time
16:07≈ on time ≈ on time
16:12≈ on time ≈ on time
16:17≈ on time ≈ on time
16:20 / 16:27≈ on time ≈ on time
16:29≈ on time ≈ on time
16:34≈ on time ≈ on time
16: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
Tue 17 NovBunnik 16:49Partial coverage+2 min+2 min
Mon 16 NovBunnik 16:49Partial coverage0 min—
Fri 13 NovBunnik 16:470 min—
Thu 12 NovBunnik 16:48Partial coverage0 min—
Wed 11 NovBunnik 16:48Partial coverage0 min—
Tue 10 NovBunnik 16:48Partial coverage0 min—
Mon 9 NovBunnik 16:54Partial coverage0 min+8 min
Sun 8 NovAmsterdam Sloterdijk 15:440 min—
Sat 7 NovAmsterdam Sloterdijk 15:440 min—
Fri 6 NovBunnik 16:47No data—
Thu 5 NovBunnik 16:48No data—
Wed 4 NovBunnik 16:48Partial coverage0 min—
Tue 3 NovBunnik 16:48Partial coverage0 min—
Mon 2 NovBunnik 16:49Partial coverage0 min—
Fri 30 OctBunnik 16:470 min—
Thu 29 OctBunnik 16:490 min—
Wed 28 OctBunnik 16:48Partial coverage0 min—
Tue 27 OctUtrecht Zuilen 16:49Partial coverage0 min—
Mon 26 OctBunnik 16:480 min—
Fri 23 OctUtrecht Zuilen 16:320 min—
Thu 22 OctAmsterdam Sloterdijk 15:460 min—
Wed 21 OctUtrecht Zuilen 16:42No data—
Tue 20 OctUtrecht Zuilen 16:430 min—
Mon 19 OctBunnik 16:460 min—
Fri 16 OctBunnik 16:470 min—
Thu 15 OctBunnik 16:48No data—
Wed 14 OctBunnik 16:48No data—
Tue 13 OctBunnik 16:50No data—
Mon 12 OctBunnik 16:490 min—
Fri 9 OctBunnik 16:470 min—