Train NS 4943 Almere Centrum – Utrecht Centraal
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 12:51 from Almere Centrum · 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
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=3
- 100% T n=2
- 100% W n=4
- 100% T n=3
- 100% F n=1
- 100% S n=4
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 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 |
|---|---|---|---|
| 12:51 | on time | on time | |
| 12:54 | — | — | |
| 12:58 | — | — | |
| 13:09 / 13:12 | — | — | |
| 13:17 / 13:18 | — | — | |
| 13:20 | — | — | |
| 13:31 | — | — | |
| 13:35 | — | — |
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 Overvecht 13:44Partial coverage | 0 min | +1 min |
| Tue 3 Nov | Utrecht Overvecht 13:44 | No data | — |
| Mon 2 Nov | Utrecht Overvecht 13:44Partial coverage | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 13:46Partial coverage | +1 min | +3 min |
| Fri 30 Oct | Utrecht Overvecht 13:45 | No data | — |
| Thu 29 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Wed 28 Oct | Utrecht Overvecht 13:48Partial coverage | 0 min | — |
| Tue 27 Oct | Utrecht Overvecht 13:45 | No data | — |
| Mon 26 Oct | Utrecht Overvecht 17:22 | No data | — |
| Sun 25 Oct | Utrecht Overvecht 13:45 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Fri 23 Oct | Utrecht Overvecht 13:45 | No data | — |
| Thu 22 Oct | Utrecht Overvecht 13:48Partial coverage | 0 min | — |
| Wed 21 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Tue 20 Oct | Utrecht Overvecht 13:45 | No data | — |
| Mon 19 Oct | Utrecht Overvecht 13:47Partial coverage | 0 min | — |
| Sun 18 Oct | Utrecht Overvecht 13:45 | 0 min | — |
| Sat 17 Oct | Utrecht Overvecht 13:56 | 0 min | — |
| Fri 16 Oct | Utrecht Overvecht 13:45 | No data | — |
| Thu 15 Oct | Utrecht Overvecht 13:45 | No data | — |
| Wed 14 Oct | Utrecht Overvecht 13:45 | No data | — |
| Tue 13 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Mon 12 Oct | Utrecht Overvecht 13:47 | No data | — |
| Sun 11 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Sat 10 Oct | Utrecht Overvecht 13:45Partial coverage | +1 min | +1 min |
| Fri 9 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Thu 8 Oct | Utrecht Overvecht 13:45Partial coverage | +1 min | +1 min |
| Wed 7 Oct | Utrecht Overvecht 13:48Partial coverage | +3 min | +3 min |
| Tue 6 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |
| Mon 5 Oct | Utrecht Overvecht 13:45Partial coverage | 0 min | — |