Train NS 4625 Amsterdam Centraal – Almere Oostvaarders
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 07:52 from Amsterdam Centraal · Thu 5 Nov
Last 30 days
Arrival delay at Almere Oostvaarders, 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 17 Oct Max en route +4 min · last fix heading to Diemen +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 95% · 19
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=4
- 100% W n=3
- 100% T n=4
- 100% F n=4
- 0% S n=1
- 100% S n=1
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 |
|---|---|---|---|
| 07:52 | on time | on time | |
| 07:58 | ≈ on time | ≈ on time | |
| 08:01 | ≈ on time | ≈ on time | |
| 08:03 | ≈ on time | ≈ on time | |
| 08:09 / 08:11 | ≈ on time | ≈ +1 min | |
| 08:17 | ≈ on time | ≈ +1 min | |
| 08:21 | ≈ on time | ≈ +1 min | |
| 08:24 / 08:25 | ≈ on time | ≈ +1 min | |
| 08:28 | ≈ on time | ≈ +2 min | |
| 08:31 | ≈ on time | ≈ +2 min | |
| 08:35 | 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 |
|---|---|---|---|
| Wed 4 Nov | Almere Buiten 08:44Partial coverage | 0 min | — |
| Tue 3 Nov | Almere Buiten 08:44Partial coverage | 0 min | — |
| Mon 2 Nov | Almere Buiten 08:44Partial coverage | 0 min | — |
| Fri 30 Oct | Almere Buiten 08:46Partial coverage | 0 min | — |
| Thu 29 Oct | Almere Buiten 08:46 | 0 min | — |
| Wed 28 Oct | Almere Buiten 08:46 | No data | — |
| Tue 27 Oct | Almere Buiten 08:45 | 0 min | — |
| Mon 26 Oct | Almere Buiten 08:46 | 0 min | +1 min |
| Fri 23 Oct | Almere Buiten 08:59 | +1 min | +1 min |
| Thu 22 Oct | Almere Buiten 08:47Partial coverage | 0 min | — |
| Wed 21 Oct | Almere Buiten 08:46Partial coverage | 0 min | — |
| Tue 20 Oct | Almere Buiten 08:46Partial coverage | 0 min | — |
| Mon 19 Oct | Almere Buiten 08:49Partial coverage | 0 min | — |
| Sun 18 Oct | Diemen 08:22 | 0 min | — |
| Sat 17 Oct | Diemen 08:22 | +4 min | +4 min |
| Fri 16 Oct | Almere Buiten 08:46 | 0 min | — |
| Thu 15 Oct | Almere Buiten 08:46 | 0 min | — |
| Wed 14 Oct | Almere Buiten 08:46 | No data | — |
| Tue 13 Oct | Almere Buiten 08:46 | No data | — |
| Mon 12 Oct | Almere Buiten 08:46 | No data | — |
| Fri 9 Oct | Almere Buiten 08:46Partial coverage | 0 min | — |
| Thu 8 Oct | Almere Buiten 08:46Partial coverage | 0 min | — |
| Wed 7 Oct | Almere Buiten 08:48 | +2 min | +4 min |
| Tue 6 Oct | Almere Buiten 08:46 | 0 min | — |
| Mon 5 Oct | Almere Buiten 08:46 | No data | — |
| Fri 2 Oct | Almere Buiten 08:45 | No data | — |
| Thu 1 Oct | Almere Buiten 08:47 | No data | — |
| Wed 30 Sept | Almere Buiten 08:46 | No data | — |
| Tue 29 Sept | Almere Buiten 08:57 | No data | — |
| Mon 28 Sept | Almere Buiten 08:45 | No data | — |