Train NS 2687 Amsterdam Centraal – Almere Centrum
Running now · updated 23:36
Heading to Almere Centrum 0 min
Estimated arrival at Almere Centrum 23:58 · 0 km/h
- Amsterdam Centraal23:38
- Almere Centrum23:58
Today it is running no worse than usual: typical arrival delay is 0 min; 73% of the last 15 runs arrived on time.
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
- Fri 16 Oct Max en route +10 min · last fix heading to — +10 min
- Mon 2 Nov Max en route +10 min · last fix heading to — +10 min
- Fri 23 Oct Max en route +7 min · last fix heading to — +7 min
- Thu 29 Oct Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 78% · 14
- 3–10 min 17% · 3
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=2
- 100% W n=3
- 67% T n=3
- 50% F n=4
- 100% S n=1
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 18 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 | Today |
|---|---|---|---|---|
| 23:38 | on time | +2 min | ||
| 23:58 | on time | +8 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 | — 23:58 | +1 min | +1 min |
| Wed 4 Nov | — 23:59 | +1 min | +1 min |
| Mon 2 Nov | — 00:12 | +10 min | +10 min |
| Sun 1 Nov | Amsterdam Centraal 23:59 | 0 min | — |
| Sat 31 Oct | — 23:59 | No data | — |
| Thu 29 Oct | — 23:59 | +5 min | +5 min |
| Wed 28 Oct | — 23:59 | No data | — |
| Tue 27 Oct | — 00:00 | 0 min | — |
| Mon 26 Oct | — 00:04 | 0 min | — |
| Sun 25 Oct | Amsterdam Centraal 23:59 | No data | — |
| Sat 24 Oct | — 00:01 | No data | — |
| Fri 23 Oct | — 00:12 | +7 min | +7 min |
| Thu 22 Oct | — 00:00 | 0 min | — |
| Wed 21 Oct | — 00:02 | 0 min | — |
| Mon 19 Oct | — 00:02 | 0 min | +1 min |
| Fri 16 Oct | — 00:19 | +10 min | +10 min |
| Thu 15 Oct | — 00:01 | No data | — |
| Wed 14 Oct | — 00:04 | No data | — |
| Tue 13 Oct | — 23:59 | No data | — |
| Mon 12 Oct | — 23:59 | 0 min | — |
| Sun 11 Oct | Amsterdam Centraal 23:52 | No data | — |
| Sat 10 Oct | — 23:59 | +1 min | +1 min |
| Fri 9 Oct | — 23:59 | 0 min | — |
| Thu 8 Oct | — 00:09 | 0 min | +5 min |
| Wed 7 Oct | — 23:59 | +1 min | +1 min |
| Tue 6 Oct | — 23:59 | 0 min | — |
| Sun 27 Sept | Amsterdam Centraal 23:53 | No data | — |
| Sat 26 Sept | Amsterdam Centraal 23:52 | No data | — |
| Sun 20 Sept | Amsterdam Centraal 23:54 | No data | — |
| Sun 30 Aug | Amsterdam Centraal 23:52 | No data | — |