Train NS 4664 Almere Oostvaarders – Amsterdam Centraal
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 18:55 from Almere Oostvaarders · Thu 5 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 +4 min · last fix heading to Amsterdam Muiderpoort +4 min
- Mon 5 Oct Max en route +4 min · last fix heading to — +4 min
- Thu 8 Oct Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 17
- 3–10 min 15% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=2
- 100% W n=1
- 67% T n=3
- 100% F n=4
- 67% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 20 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 |
|---|---|---|---|
| 18:55 | on time | on time | |
| 18:57 | ≈ on time | ≈ on time | |
| 19:01 | ≈ on time | ≈ on time | |
| 19:04 / 19:05 | ≈ on time | ≈ +1 min | |
| 19:08 | ≈ on time | ≈ +1 min | |
| 19:12 | ≈ on time | ≈ +1 min | |
| 19:19 / 19:21 | ≈ on time | ≈ +2 min | |
| 19:26 | ≈ on time | ≈ +2 min | |
| 19:28 | ≈ on time | ≈ +3 min | |
| 19:31 | ≈ on time | ≈ +3 min | |
| 19:37 | 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 |
|---|---|---|---|
| Wed 4 Nov | — 19:39 | No data | — |
| Mon 2 Nov | — 19:39 | 0 min | — |
| Sun 1 Nov | Amsterdam Muiderpoort 19:44Partial coverage | 0 min | — |
| Sat 31 Oct | Amsterdam Muiderpoort 19:46Partial coverage | +1 min | +1 min |
| Fri 30 Oct | — 19:38 | 0 min | — |
| Thu 29 Oct | — 19:39 | 0 min | — |
| Wed 28 Oct | — 19:41 | No data | — |
| Tue 27 Oct | — 19:39 | 0 min | — |
| Mon 26 Oct | — 19:38 | No data | — |
| Sun 25 Oct | Amsterdam Muiderpoort 19:46 | No data | — |
| Sat 24 Oct | Amsterdam Muiderpoort 19:45Partial coverage | 0 min | — |
| Fri 23 Oct | Amsterdam Science Park 19:42Partial coverage | +1 min | — |
| Thu 22 Oct | — 19:49 | 0 min | — |
| Wed 21 Oct | — 19:39 | No data | — |
| Mon 19 Oct | — 19:39 | 0 min | — |
| Sun 18 Oct | Schiphol Airport 20:14 | 0 min | — |
| Sat 17 Oct | Schiphol Airport 20:14 | No data | — |
| Fri 16 Oct | Amsterdam Muiderpoort 19:45Partial coverage | 0 min | — |
| Thu 15 Oct | — 19:38 | No data | — |
| Wed 14 Oct | Amsterdam Muiderpoort 19:42 | No data | — |
| Tue 13 Oct | — 19:38 | No data | — |
| Mon 12 Oct | — 19:39 | 0 min | — |
| Sun 11 Oct | Amsterdam Muiderpoort 19:48 | +3 min | +3 min |
| Sat 10 Oct | Amsterdam Muiderpoort 19:48Partial coverage | +4 min | +4 min |
| Fri 9 Oct | — 19:38 | +1 min | — |
| Thu 8 Oct | — 19:40 | +4 min | +4 min |
| Wed 7 Oct | — 19:38 | +1 min | — |
| Tue 6 Oct | — 19:38 | 0 min | — |
| Mon 5 Oct | — 19:38 | +4 min | +4 min |
| Sat 26 Sept | Amsterdam Muiderpoort 19:44 | No data | — |