Train NS 2652 Almere Centrum → Amsterdam Centraal
NS 2652 Almere Centrum–Amsterdam Centraal: final delay under 3 min on 16 of its 17 runs with data in the last 30 days (94%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 23:30 (GMT+1).
An alert on this phone or computer when the 2652 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November +2 min
Next service: Monday 16:01 from Almere Centrum · Mon 23 Nov
Last 30 days
Arrival delay at Amsterdam 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 +25 min · last fix heading to Almere Centrum +25 min
- Wed 11 Nov Max en route +4 min · last fix heading to Almere Centrum +4 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 25
- 3–10 min 4% · 1
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=3
- 67% W n=3
- 100% T n=5
- 100% F n=5
- 80% S n=5
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 16:01 | on time | on time | |
| 16:22 | 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 |
|---|---|---|---|
| Fri 20 Nov | Almere Centrum 16:24Partial coverage | +2 min | +2 min |
| Thu 19 Nov | Almere Centrum 16:24Partial coverage | +1 min | — |
| Wed 18 Nov | Almere Centrum 16:23Partial coverage | 0 min | — |
| Tue 17 Nov | Almere Centrum 16:23 | No data | — |
| Mon 16 Nov | Almere Centrum 16:24Partial coverage | 0 min | — |
| Sun 15 Nov | Almere Centrum 16:14 | No data | — |
| Sat 14 Nov | Almere Centrum 16:27 | +2 min | +2 min |
| Fri 13 Nov | Almere Centrum 16:24Partial coverage | 0 min | — |
| Thu 12 Nov | Almere Centrum 16:24Partial coverage | 0 min | — |
| Wed 11 Nov | Almere Centrum 16:29Partial coverage | +4 min | +4 min |
| Tue 10 Nov | — 16:23 | No data | — |
| Mon 9 Nov | Almere Centrum 16:24 | No data | — |
| Sun 8 Nov | Almere Centrum 16:24 | 0 min | — |
| Sat 7 Nov | Almere Centrum 16:23 | 0 min | — |
| Fri 6 Nov | Almere Centrum 16:23 | No data | — |
| Thu 5 Nov | Almere Centrum 16:24 | No data | — |
| Wed 4 Nov | Almere Centrum 16:24Partial coverage | +2 min | +2 min |
| Tue 3 Nov | Almere Centrum 16:23Partial coverage | 0 min | — |
| Mon 2 Nov | Almere Centrum 16:14 | No data | — |
| Sun 1 Nov | Almere Centrum 16:23 | 0 min | — |
| Sat 31 Oct | Almere Centrum 16:23 | 0 min | — |
| Fri 30 Oct | Almere Centrum 16:23 | No data | — |
| Thu 29 Oct | Almere Centrum 16:23Partial coverage | 0 min | — |
| Wed 28 Oct | Almere Centrum 16:25 | No data | — |
| Tue 27 Oct | Almere Centrum 16:23 | No data | — |
| Mon 26 Oct | Almere Centrum 16:26 | No data | — |
| Sun 25 Oct | Almere Centrum 16:33 | No data | — |
| Sat 24 Oct | Almere Centrum 16:23 | 0 min | — |
| Fri 23 Oct | Amsterdam Muiderpoort 16:35 | 0 min | — |
| Thu 22 Oct | Almere Centrum 16:23Partial coverage | 0 min | — |