Train NS 4923 Almere Centrum – Utrecht Centraal
✓ Today’s run finished
Today, last fix heading to Utrecht Overvecht at 08:49 No data
- Almere Centrum07:51
- Almere Muziekwijk07:54
- Almere Poort07:58
- Hilversum08:17
- Hilversum Sportpark08:20
- Utrecht Overvecht08:31
- Utrecht Centraal08:35
Next service: tomorrow 07:51 from Almere Centrum · Fri 6 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 17 Oct Max en route +4 min · last fix heading to Utrecht Overvecht +3 min
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 16
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=2
- 100% W n=3
- 100% T n=2
- 100% F n=2
- 75% S n=4
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 17 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 |
|---|---|---|---|
| 07:51 | on time | on time | |
| 07:54 | ≈ on time | ≈ on time | |
| 07:58 | ≈ on time | ≈ on time | |
| 08:09 / 08:12 | ≈ on time | ≈ +1 min | |
| 08:17 / 08:18 | ≈ on time | ≈ +1 min | |
| 08:20 | ≈ on time | ≈ +1 min | |
| 08:31 | ≈ on time | ≈ +1 min | |
| 08:35 | 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 |
|---|---|---|---|
| Thu 5 Nov | Utrecht Overvecht 08:49 | No data | — |
| Wed 4 Nov | Utrecht Overvecht 08:44Partial coverage | 0 min | — |
| Tue 3 Nov | Utrecht Overvecht 08:49 | No data | — |
| Mon 2 Nov | Utrecht Overvecht 08:47Partial coverage | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 08:47 | +1 min | +1 min |
| Fri 30 Oct | Utrecht Overvecht 08:46 | No data | — |
| Thu 29 Oct | Utrecht Overvecht 08:50 | 0 min | — |
| Wed 28 Oct | Utrecht Overvecht 08:45 | No data | — |
| Tue 27 Oct | Utrecht Overvecht 08:45 | 0 min | — |
| Mon 26 Oct | Utrecht Overvecht 08:45 | 0 min | — |
| Sat 24 Oct | Utrecht Overvecht 08:47 | +1 min | — |
| Fri 23 Oct | Utrecht Overvecht 08:47Partial coverage | 0 min | — |
| Thu 22 Oct | Utrecht Overvecht 08:48 | No data | — |
| Wed 21 Oct | Utrecht Overvecht 08:45 | No data | — |
| Tue 20 Oct | Utrecht Overvecht 08:47 | No data | — |
| Mon 19 Oct | Utrecht Overvecht 08:45Partial coverage | 0 min | — |
| Sat 17 Oct | Utrecht Overvecht 08:48 | +3 min | +4 min |
| Fri 16 Oct | Utrecht Overvecht 08:45 | No data | — |
| Thu 15 Oct | Utrecht Overvecht 08:45 | No data | — |
| Wed 14 Oct | Utrecht Overvecht 08:45Partial coverage | 0 min | — |
| Tue 13 Oct | Utrecht Overvecht 08:46 | No data | — |
| Mon 12 Oct | Utrecht Overvecht 08:46 | 0 min | — |
| Sat 10 Oct | Utrecht Overvecht 08:46 | 0 min | — |
| Fri 9 Oct | Utrecht Overvecht 08:48Partial coverage | +2 min | +3 min |
| Thu 8 Oct | Utrecht Overvecht 08:45Partial coverage | 0 min | +1 min |
| Wed 7 Oct | Utrecht Overvecht 08:46Partial coverage | +1 min | +2 min |
| Tue 6 Oct | Utrecht Overvecht 08:47Partial coverage | +2 min | +3 min |
| Mon 5 Oct | Utrecht Overvecht 08:45 | No data | — |
| Sat 3 Oct | Utrecht Overvecht 08:46 | No data | — |
| Fri 2 Oct | Utrecht Overvecht 08:45 | No data | — |