Train NS 7433 Uitgeest – Utrecht Centraal
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 09:03 from Uitgeest · Mon 9 Nov
Last 30 days
Arrival delay at Utrecht Centraal, 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
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 19
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 100% W n=4
- 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 (18 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 09:03 | on time | on time | |
| 09:08 | ≈ on time | ≈ on time | |
| 09:10 / 09:16 | ≈ on time | ≈ on time | |
| 09:19 | ≈ on time | ≈ on time | |
| 09:22 | ≈ on time | ≈ on time | |
| 09:25 | ≈ on time | ≈ on time | |
| 09:31 | ≈ on time | ≈ on time | |
| 09:37 / 09:39 | ≈ on time | ≈ on time | |
| 09:44 | ≈ on time | ≈ on time | |
| 09:48 | ≈ on time | ≈ on time | |
| 09:51 | ≈ on time | ≈ on time | |
| 09:54 | ≈ on time | ≈ on time | |
| 09:56 | ≈ on time | ≈ on time | |
| 10:00 | ≈ on time | ≈ on time | |
| 10:07 | ≈ on time | ≈ on time | |
| 10:12 | ≈ on time | ≈ on time | |
| 10:17 | ≈ on time | ≈ on time | |
| 10:20 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Duivendrecht 09:59 | No data | — |
| Thu 5 Nov | Utrecht Zuilen 10:59 | No data | — |
| Wed 4 Nov | Utrecht Zuilen 10:29Partial coverage | 0 min | — |
| Tue 3 Nov | Utrecht Zuilen 10:29Partial coverage | 0 min | — |
| Mon 2 Nov | Utrecht Zuilen 10:29Partial coverage | 0 min | — |
| Fri 30 Oct | Utrecht Zuilen 10:35 | 0 min | — |
| Thu 29 Oct | Utrecht Zuilen 10:36Partial coverage | 0 min | — |
| Wed 28 Oct | Utrecht Zuilen 14:35 | No data | — |
| Tue 27 Oct | Utrecht Zuilen 10:31Partial coverage | 0 min | — |
| Mon 26 Oct | Amsterdam Centraal 09:53Partial coverage | 0 min | — |
| Fri 23 Oct | Utrecht Zuilen 10:35Partial coverage | 0 min | — |
| Thu 22 Oct | Amsterdam Sloterdijk 09:46Partial coverage | 0 min | — |
| Wed 21 Oct | Utrecht Zuilen 15:15 | 0 min | — |
| Tue 20 Oct | Utrecht Zuilen 10:31Partial coverage | 0 min | — |
| Mon 19 Oct | Utrecht Zuilen 10:31Partial coverage | 0 min | — |
| Fri 16 Oct | Utrecht Zuilen 10:36 | 0 min | — |
| Thu 15 Oct | Amsterdam Sloterdijk 10:58 | No data | — |
| Wed 14 Oct | Utrecht Zuilen 10:31 | 0 min | — |
| Tue 13 Oct | Utrecht Zuilen 10:38 | No data | — |
| Mon 12 Oct | Utrecht Zuilen 10:31 | 0 min | — |
| Fri 9 Oct | Utrecht Zuilen 10:36 | +1 min | +2 min |
| Thu 8 Oct | Utrecht Zuilen 10:31Partial coverage | 0 min | — |
| Wed 7 Oct | Utrecht Zuilen 10:35Partial coverage | +1 min | +1 min |
| Tue 6 Oct | Utrecht Zuilen 10:31Partial coverage | +2 min | +2 min |
| Mon 5 Oct | Ede-Wageningen 11:13 | No data | — |
| Fri 2 Oct | Utrecht Zuilen 10:35 | No data | — |
| Thu 1 Oct | Utrecht Zuilen 10:31 | No data | — |
| Wed 30 Sept | Utrecht Zuilen 10:32 | No data | — |
| Tue 29 Sept | Utrecht Zuilen 10:32 | No data | — |
| Mon 28 Sept | Utrecht Zuilen 10:31 | No data | — |