Train NS 2653 Amsterdam Centraal → Almere Centrum
NS 2653 Amsterdam Centraal–Almere Centrum: final delay under 3 min on 14 of its 15 runs with data in the last 30 days (93%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 04:20 (GMT+1).
An alert on this phone or computer when the 2653 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 +1 min
Next service: tomorrow 15:08 from Amsterdam Centraal · Mon 23 Nov
Last 30 days
Arrival delay at Almere Centrum, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 19 Nov Max en route +11 min · last fix heading to Amsterdam Centraal +11 min
- Sat 10 Oct Max en route +6 min · last fix heading to Amsterdam Centraal +6 min
Distribution · 90 days
25 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 23
- 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=2
- 100% W n=3
- 80% T n=5
- 100% F n=4
- 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, 25 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 |
|---|---|---|---|
| 15:08 | on time | on time | |
| 15:28 | on time | +5 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 | Amsterdam Centraal 15:32Partial coverage | +1 min | +1 min |
| Thu 19 Nov | Amsterdam Centraal 15:49 | +11 min | +11 min |
| Wed 18 Nov | Amsterdam Centraal 15:29Partial coverage | No data | — |
| Tue 17 Nov | Amsterdam Centraal 15:22 | No data | — |
| Mon 16 Nov | Amsterdam Centraal 15:59 | 0 min | — |
| Sun 15 Nov | Amsterdam Centraal 15:29Partial coverage | No data | — |
| Sat 14 Nov | Amsterdam Centraal 15:28Partial coverage | +1 min | +1 min |
| Fri 13 Nov | Amsterdam Centraal 15:29 | +1 min | +1 min |
| Thu 12 Nov | Amsterdam Centraal 15:34 | +2 min | +3 min |
| Wed 11 Nov | Amsterdam Centraal 15:29 | 0 min | — |
| Tue 10 Nov | — 15:29 | No data | — |
| Mon 9 Nov | Amsterdam Centraal 15:29 | 0 min | — |
| Sun 8 Nov | Amsterdam Centraal 15:29Partial coverage | 0 min | — |
| Sat 7 Nov | Amsterdam Centraal 15:28Partial coverage | 0 min | — |
| Fri 6 Nov | Amsterdam Centraal 15:29 | No data | — |
| Thu 5 Nov | Amsterdam Centraal 15:29 | No data | — |
| Wed 4 Nov | Amsterdam Centraal 15:29 | 0 min | — |
| Tue 3 Nov | Amsterdam Centraal 15:29 | No data | — |
| Mon 2 Nov | Amsterdam Centraal 15:34 | No data | — |
| Sun 1 Nov | Amsterdam Centraal 15:30Partial coverage | 0 min | — |
| Sat 31 Oct | Amsterdam Centraal 15:29Partial coverage | 0 min | — |
| Fri 30 Oct | Amsterdam Centraal 15:29 | No data | — |
| Thu 29 Oct | Amsterdam Centraal 15:29 | No data | — |
| Wed 28 Oct | Amsterdam Centraal 15:40 | 0 min | — |
| Tue 27 Oct | Amsterdam Centraal 15:30 | No data | — |
| Mon 26 Oct | Amsterdam Centraal 15:29 | No data | — |
| Sun 25 Oct | Amsterdam Centraal 15:35 | No data | — |
| Sat 24 Oct | Amsterdam Centraal 15:28 | 0 min | — |
| Fri 23 Oct | Amsterdam Centraal 15:29 | 0 min | — |
| Thu 22 Oct | Amsterdam Centraal 15:32Partial coverage | 0 min | — |