Train NS 4975 Almere Centrum – Utrecht Centraal
It has not run yet today
Last recorded run: Saturday 14 November 0 min
Next service: today 20:51 from Almere Centrum · Sun 15 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
- Sat 10 Oct Max en route +6 min · last fix heading to Utrecht Overvecht +6 min
- Fri 13 Nov Max en route +6 min · last fix heading to — +6 min
- Fri 9 Oct Max en route +4 min · last fix heading to — +4 min
- Thu 8 Oct Max en route +4 min · last fix heading to — +4 min
- Sun 8 Nov Max en route +3 min · last fix heading to Utrecht Overvecht +3 min
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 82% · 23
- 3–10 min 18% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=3
- 67% T n=3
- 60% F n=5
- 75% S n=4
- 75% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 20:51 | on time | on time | |
| 20:54 | ≈ on time | ≈ on time | |
| 20:58 | ≈ on time | ≈ +1 min | |
| 21:09 / 21:11 | ≈ on time | ≈ +2 min | |
| 21:16 / 21:17 | ≈ on time | ≈ +2 min | |
| 21:20 | ≈ on time | ≈ +3 min | |
| 21:24 | ≈ on time | ≈ +3 min | |
| 21:32 | ≈ on time | ≈ +4 min | |
| 21:36 | on time | +4 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 |
|---|---|---|---|
| Sat 14 Nov | Utrecht Overvecht 21:44Partial coverage | 0 min | — |
| Fri 13 Nov | — 21:48 | +6 min | +6 min |
| Thu 12 Nov | — 21:37 | 0 min | — |
| Wed 11 Nov | — 21:37 | 0 min | — |
| Tue 10 Nov | — 21:04 | 0 min | — |
| Mon 9 Nov | — 21:37 | 0 min | — |
| Sun 8 Nov | Utrecht Overvecht 21:49Partial coverage | +3 min | +3 min |
| Sat 7 Nov | Utrecht Overvecht 21:44Partial coverage | 0 min | — |
| Fri 6 Nov | — 21:39 | +1 min | +2 min |
| Thu 5 Nov | — 21:38 | No data | — |
| Wed 4 Nov | — 21:38 | +1 min | — |
| Tue 3 Nov | — 21:38 | No data | — |
| Mon 2 Nov | — 21:39 | +1 min | +2 min |
| Sun 1 Nov | Utrecht Overvecht 21:47Partial coverage | +1 min | — |
| Sat 31 Oct | Utrecht Overvecht 21:51 | No data | — |
| Fri 30 Oct | — 21:40 | No data | — |
| Thu 29 Oct | — 21:37 | 0 min | — |
| Wed 28 Oct | — 21:37 | No data | — |
| Tue 27 Oct | — 21:52 | 0 min | — |
| Mon 26 Oct | — 21:39 | No data | — |
| Sun 25 Oct | Utrecht Overvecht 21:49 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 21:47 | No data | — |
| Fri 23 Oct | — 21:40 | +1 min | +1 min |
| Thu 22 Oct | — 21:40 | No data | — |
| Wed 21 Oct | — 21:37 | No data | — |
| Tue 20 Oct | — 21:44 | No data | — |
| Mon 19 Oct | — 21:42 | 0 min | — |
| Sun 18 Oct | Utrecht Overvecht 21:45 | 0 min | — |
| Sat 17 Oct | Utrecht Overvecht 21:45 | 0 min | — |
| Fri 16 Oct | — 21:51 | +2 min | +2 min |