Train NS 4929 Almere Centrum – Utrecht Centraal
✓ Today’s run finished
Today, last fix heading to Utrecht Overvecht at 10:17 No data
- Almere Centrum09:21
- Almere Muziekwijk09:24
- Almere Poort09:28
- Hilversum09:47
- Hilversum Sportpark09:50
- Utrecht Overvecht10:01
- Utrecht Centraal10:05
Next service: tomorrow 09:21 from Almere Centrum · Sat 7 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 +6 min · last fix heading to Utrecht Overvecht +6 min
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 21
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=3
- 100% W n=4
- 100% T n=2
- 100% F n=3
- 75% 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, 22 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:21 | on time | on time | |
| 09:24 | ≈ on time | ≈ on time | |
| 09:28 | ≈ on time | ≈ on time | |
| 09:39 / 09:42 | ≈ on time | ≈ +1 min | |
| 09:47 / 09:48 | ≈ on time | ≈ +2 min | |
| 09:50 | ≈ on time | ≈ +2 min | |
| 10:01 | ≈ on time | ≈ +3 min | |
| 10:05 | 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 |
|---|---|---|---|
| Fri 6 Nov | Utrecht Overvecht 10:17 | No data | — |
| Thu 5 Nov | Utrecht Overvecht 10:14 | No data | — |
| Wed 4 Nov | Utrecht Overvecht 10:14Partial coverage | 0 min | — |
| Tue 3 Nov | Utrecht Overvecht 10:14Partial coverage | 0 min | — |
| Mon 2 Nov | Utrecht Overvecht 10:14Partial coverage | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 10:16 | 0 min | — |
| Fri 30 Oct | Utrecht Overvecht 10:15 | No data | — |
| Thu 29 Oct | Utrecht Overvecht 10:19Partial coverage | 0 min | — |
| Wed 28 Oct | Utrecht Overvecht 10:16 | No data | — |
| Tue 27 Oct | Utrecht Overvecht 10:15 | No data | — |
| Mon 26 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Sun 25 Oct | Utrecht Overvecht 10:16 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 10:17 | +1 min | +1 min |
| Fri 23 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Thu 22 Oct | Utrecht Overvecht 10:15 | No data | — |
| Wed 21 Oct | Utrecht Overvecht 10:15 | 0 min | — |
| Tue 20 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Mon 19 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Sun 18 Oct | Utrecht Overvecht 10:15 | 0 min | — |
| Sat 17 Oct | Utrecht Overvecht 10:15 | +6 min | +6 min |
| Fri 16 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Thu 15 Oct | Almere Poort 10:58 | No data | — |
| Wed 14 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Tue 13 Oct | Utrecht Overvecht 10:16 | No data | — |
| Mon 12 Oct | Utrecht Overvecht 10:15Partial coverage | 0 min | — |
| Sun 11 Oct | Utrecht Overvecht 10:16 | 0 min | — |
| Sat 10 Oct | Utrecht Overvecht 10:16 | 0 min | — |
| Fri 9 Oct | Utrecht Overvecht 10:16Partial coverage | 0 min | — |
| Thu 8 Oct | Utrecht Overvecht 10:15Partial coverage | +1 min | — |
| Wed 7 Oct | Utrecht Overvecht 10:17Partial coverage | 0 min | +1 min |