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