Train NS 4642 Almere Oostvaarders – Amsterdam Centraal
It has not run yet today
Last recorded run: Wednesday 4 November +1 min
Next service: today 13:25 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 +23 min · last fix heading to Diemen +22 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 94% · 17
- 3–10 min 0% · 0
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=2
- 100% W n=2
- 100% T n=3
- 100% F n=2
- 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, 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 |
|---|---|---|---|
| 13:25 | on time | on time | |
| 13:27 | ≈ on time | ≈ on time | |
| 13:31 | ≈ on time | ≈ on time | |
| 13:34 / 13:35 | ≈ on time | ≈ +1 min | |
| 13:38 | ≈ on time | ≈ +1 min | |
| 13:42 | ≈ on time | ≈ +1 min | |
| 13:49 / 13:51 | ≈ on time | ≈ +2 min | |
| 13:56 | ≈ on time | ≈ +2 min | |
| 13:59 | ≈ on time | ≈ +2 min | |
| 14:01 | ≈ on time | ≈ +2 min | |
| 14:07 | 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 | Amsterdam Muiderpoort 14:14Partial coverage | +1 min | — |
| Tue 3 Nov | Amsterdam Muiderpoort 14:17 | No data | — |
| Mon 2 Nov | Amsterdam Muiderpoort 14:14 | No data | — |
| Sun 1 Nov | Amsterdam Muiderpoort 14:17Partial coverage | +1 min | — |
| Sat 31 Oct | Amsterdam Muiderpoort 14:16Partial coverage | +1 min | — |
| Fri 30 Oct | Amsterdam Muiderpoort 14:15 | No data | — |
| Thu 29 Oct | Amsterdam Muiderpoort 14:16Partial coverage | 0 min | — |
| Wed 28 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Tue 27 Oct | Almere Poort 14:46Partial coverage | 0 min | — |
| Mon 26 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Sun 25 Oct | Amsterdam Muiderpoort 14:20 | No data | — |
| Sat 24 Oct | Amsterdam Muiderpoort 14:19 | +3 min | +4 min |
| Fri 23 Oct | Amsterdam Muiderpoort 14:19 | 0 min | — |
| Thu 22 Oct | Amsterdam Muiderpoort 14:15Partial coverage | 0 min | — |
| Wed 21 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Tue 20 Oct | Amsterdam Muiderpoort 14:15 | No data | — |
| Mon 19 Oct | Amsterdam Muiderpoort 14:16 | 0 min | — |
| Sun 18 Oct | Schiphol Airport 14:49 | +3 min | +3 min |
| Sat 17 Oct | Schiphol Airport 14:46 | No data | — |
| Fri 16 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Thu 15 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Wed 14 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Tue 13 Oct | Amsterdam Muiderpoort 14:16 | No data | — |
| Mon 12 Oct | Amsterdam Muiderpoort 14:16Partial coverage | 0 min | — |
| Sun 11 Oct | Amsterdam Muiderpoort 14:17Partial coverage | +1 min | +2 min |
| Sat 10 Oct | Diemen 14:48Partial coverage | +22 min | +23 min |
| Fri 9 Oct | Amsterdam Muiderpoort 14:16Partial coverage | +1 min | — |
| Thu 8 Oct | Amsterdam Muiderpoort 14:15Partial coverage | 0 min | — |
| Wed 7 Oct | Amsterdam Muiderpoort 14:16 | +1 min | — |
| Tue 6 Oct | Amsterdam Muiderpoort 14:16 | 0 min | — |