Train NS 7431 Uitgeest – Utrecht Centraal
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 08:33 from Uitgeest · Thu 5 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
Worst days
- Fri 9 Oct Max en route +5 min · last fix heading to Utrecht Zuilen +4 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 14
- 3–10 min 7% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 100% W n=4
- 100% T n=3
- 75% 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, 15 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 |
|---|---|---|---|
| 08:33 | on time | on time | |
| 08:38 | ≈ on time | ≈ on time | |
| 08:40 / 08:46 | ≈ on time | ≈ on time | |
| 08:49 | ≈ on time | ≈ +1 min | |
| 08:52 | ≈ on time | ≈ +1 min | |
| 08:55 | ≈ on time | ≈ +1 min | |
| 09:01 | ≈ on time | ≈ +1 min | |
| 09:07 / 09:09 | ≈ on time | ≈ +1 min | |
| 09:14 | ≈ on time | ≈ +1 min | |
| 09:18 | ≈ on time | ≈ +2 min | |
| 09:21 | ≈ on time | ≈ +2 min | |
| 09:24 | ≈ on time | ≈ +2 min | |
| 09:26 | ≈ on time | ≈ +2 min | |
| 09:30 | ≈ on time | ≈ +2 min | |
| 09:37 | ≈ on time | ≈ +2 min | |
| 09:42 | ≈ on time | ≈ +2 min | |
| 09:47 | ≈ on time | ≈ +2 min | |
| 09:50 | on time | +3 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 |
|---|---|---|---|
| Wed 4 Nov | Utrecht Zuilen 09:59Partial coverage | 0 min | — |
| Tue 3 Nov | Utrecht Zuilen 09:59 | No data | — |
| Mon 2 Nov | Utrecht Zuilen 10:02 | No data | — |
| Fri 30 Oct | Utrecht Zuilen 10:05 | 0 min | — |
| Thu 29 Oct | Utrecht Zuilen 10:05Partial coverage | 0 min | — |
| Wed 28 Oct | Utrecht Zuilen 10:01Partial coverage | 0 min | — |
| Tue 27 Oct | Utrecht Zuilen 10:01 | No data | — |
| Mon 26 Oct | Abcoude 09:44Partial coverage | 0 min | — |
| Fri 23 Oct | Utrecht Zuilen 10:01 | 0 min | — |
| Thu 22 Oct | Amsterdam Sloterdijk 09:16Partial coverage | 0 min | — |
| Wed 21 Oct | Utrecht Zuilen 10:07 | No data | — |
| Tue 20 Oct | Utrecht Zuilen 10:01Partial coverage | 0 min | — |
| Mon 19 Oct | Utrecht Zuilen 10:01Partial coverage | 0 min | — |
| Fri 16 Oct | Utrecht Zuilen 10:05 | 0 min | — |
| Thu 15 Oct | Amsterdam Holendrecht 10:58 | No data | — |
| Wed 14 Oct | Utrecht Zuilen 10:02 | 0 min | — |
| Tue 13 Oct | Utrecht Zuilen 10:02 | No data | — |
| Mon 12 Oct | Utrecht Zuilen 10:02 | No data | — |
| Fri 9 Oct | Utrecht Zuilen 10:11 | +4 min | +5 min |
| Thu 8 Oct | Utrecht Zuilen 10:01Partial coverage | 0 min | — |
| Wed 7 Oct | Utrecht Zuilen 10:03Partial coverage | +2 min | +2 min |
| Tue 6 Oct | Utrecht Zuilen 10:01Partial coverage | 0 min | — |
| Mon 5 Oct | Ede-Wageningen 10:43 | No data | — |
| Fri 2 Oct | Utrecht Zuilen 10:05 | No data | — |
| Thu 1 Oct | Utrecht Zuilen 10:01 | No data | — |
| Wed 30 Sept | Utrecht Zuilen 10:01 | No data | — |
| Tue 29 Sept | Utrecht Zuilen 10:01 | No data | — |
| Mon 28 Sept | Utrecht Zuilen 10:11 | No data | — |
| Fri 25 Sept | Utrecht Zuilen 10:06 | No data | — |
| Thu 24 Sept | Utrecht Zuilen 10:01 | No data | — |