Train NS 7465 Uitgeest – Driebergen-Zeist
It does not run today
Last recorded run: Friday 13 November +2 min
Next service: tomorrow 17:03 from Uitgeest · Mon 16 Nov
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 29 Oct Max en route +5 min · last fix heading to Abcoude +5 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=6
- 100% T n=3
- 100% W n=3
- 75% T n=4
- 100% F n=6
- 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, 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:03 | on time | on time | |
| 17:08 | ≈ on time | ≈ on time | |
| 17:11 | ≈ on time | ≈ on time | |
| 17:14 | ≈ on time | ≈ on time | |
| 17:17 | ≈ on time | ≈ on time | |
| 17:20 | ≈ on time | ≈ on time | |
| 17:26 | ≈ on time | ≈ on time | |
| 17:32 / 17:34 | ≈ on time | ≈ on time | |
| 17:40 | ≈ on time | ≈ on time | |
| 17:43 | ≈ on time | ≈ on time | |
| 17:46 | ≈ on time | ≈ on time | |
| 17:49 / 17:57 | ≈ on time | ≈ on time | |
| 18:00 | ≈ on time | ≈ on time | |
| 18:03 | ≈ on time | ≈ on time | |
| 18:11 | ≈ on time | ≈ on time | |
| 18:16 | ≈ on time | ≈ on time | |
| 18:21 | ≈ on time | ≈ on time | |
| 18:24 / 18:26 | ≈ on time | ≈ on time | |
| 18:28 | ≈ on time | ≈ on time | |
| 18:33 | ≈ on time | ≈ on time | |
| 18:37 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 13 Nov | Bunnik 18:47Partial coverage | +2 min | +2 min |
| Thu 12 Nov | Utrecht Zuilen 18:39 | 0 min | — |
| Wed 11 Nov | Maarssen 18:39 | 0 min | — |
| Tue 10 Nov | Utrecht Zuilen 18:39 | 0 min | — |
| Mon 9 Nov | Maarssen 18:39 | 0 min | — |
| Sun 8 Nov | Amsterdam Sloterdijk 17:47 | +2 min | +2 min |
| Sat 7 Nov | Amsterdam Sloterdijk 17:44 | 0 min | — |
| Fri 6 Nov | Bunnik 18:44Partial coverage | +1 min | — |
| Thu 5 Nov | Maarssen 18:39 | No data | — |
| Wed 4 Nov | Maarssen 18:39 | No data | — |
| Tue 3 Nov | Maarssen 18:39 | No data | — |
| Mon 2 Nov | Breukelen 18:39 | 0 min | — |
| Fri 30 Oct | Bunnik 18:47Partial coverage | 0 min | — |
| Thu 29 Oct | Abcoude 18:47 | +5 min | +5 min |
| Wed 28 Oct | Maarssen 18:40 | 0 min | — |
| Tue 27 Oct | Abcoude 18:40 | No data | — |
| Mon 26 Oct | Breukelen 18:40 | 0 min | — |
| Fri 23 Oct | Utrecht Zuilen 18:31 | 0 min | — |
| Thu 22 Oct | Amsterdam Sloterdijk 17:44 | 0 min | — |
| Wed 21 Oct | Utrecht Zuilen 18:41 | No data | — |
| Tue 20 Oct | Utrecht Zuilen 18:41 | 0 min | — |
| Mon 19 Oct | Bunnik 18:46 | 0 min | — |
| Fri 16 Oct | Bunnik 18:47 | 0 min | — |
| Thu 15 Oct | Utrecht Vaartsche Rijn 18:43 | No data | — |
| Wed 14 Oct | Bunnik 18:48 | No data | — |
| Tue 13 Oct | Bunnik 18:48 | No data | — |
| Mon 12 Oct | Bunnik 18:48 | 0 min | — |
| Fri 9 Oct | Bunnik 18:47Partial coverage | +1 min | — |
| Thu 8 Oct | Abcoude 18:40 | 0 min | — |
| Wed 7 Oct | Breukelen 18:40 | 0 min | — |