Train NS 2691 Amsterdam Centraal – Almere Centrum
✓ Today’s run finished
Today, last fix heading to — at 00:59 0 min
- Amsterdam Centraal00:38
- Almere Centrum00:58
Next service: Friday 00:38 from Amsterdam Centraal · Fri 13 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
Distribution · 90 days
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 6
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 100% S n=4
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 6 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 |
|---|---|---|---|
| 00:38 | on time | on time | |
| 00:58 | on time | +2 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 |
|---|---|---|---|
| Sat 7 Nov | — 00:59 | 0 min | — |
| Sun 25 Oct | — 00:58 | 0 min | — |
| Sat 24 Oct | — 01:06 | 0 min | — |
| Sat 17 Oct | — 01:04 | +2 min | +3 min |
| Sun 11 Oct | — 01:02 | +2 min | +3 min |
| Sat 10 Oct | — 01:00 | 0 min | — |