Train NS 4668 Almere Oostvaarders – Amsterdam Centraal
✓ Today’s run finished
Today, last fix heading to Amsterdam Muiderpoort at 20:44 0 min
- Almere Oostvaarders19:55
- Almere Parkwijk20:01
- Almere Centrum20:04
- Almere Poort20:12
- Diemen20:26
- Amsterdam Muiderpoort20:32
- Amsterdam Centraal20:37
Next service: tomorrow 19:55 from Almere Oostvaarders · Sun 15 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 +9 min · last fix heading to Amsterdam Muiderpoort +9 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 26
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=2
- 100% W n=3
- 100% T n=4
- 100% F n=5
- 83% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 19:55 | on time | on time | |
| 19:57 | ≈ on time | ≈ on time | |
| 20:01 | ≈ on time | ≈ on time | |
| 20:04 / 20:05 | ≈ on time | ≈ on time | |
| 20:08 | ≈ on time | ≈ +1 min | |
| 20:12 | ≈ on time | ≈ +1 min | |
| 20:19 / 20:21 | ≈ on time | ≈ +1 min | |
| 20:26 | ≈ on time | ≈ +1 min | |
| 20:28 | ≈ on time | ≈ +1 min | |
| 20:32 | ≈ on time | ≈ +2 min | |
| 20:37 | 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 14 Nov | Amsterdam Muiderpoort 20:44Partial coverage | 0 min | — |
| Fri 13 Nov | — 20:39 | 0 min | — |
| Thu 12 Nov | — 20:39 | +1 min | — |
| Wed 11 Nov | — 20:38 | +2 min | +2 min |
| Mon 9 Nov | — 20:38 | 0 min | — |
| Sun 8 Nov | Amsterdam Muiderpoort 20:44 | 0 min | — |
| Sat 7 Nov | Amsterdam Muiderpoort 20:44 | 0 min | — |
| Fri 6 Nov | — 20:39 | 0 min | — |
| Thu 5 Nov | — 20:39 | No data | — |
| Wed 4 Nov | — 20:39 | +1 min | +1 min |
| Tue 3 Nov | — 20:38 | No data | — |
| Sun 1 Nov | Amsterdam Muiderpoort 20:44 | 0 min | — |
| Sat 31 Oct | Amsterdam Muiderpoort 20:45 | 0 min | — |
| Fri 30 Oct | — 20:38 | No data | — |
| Thu 29 Oct | — 20:38 | 0 min | +2 min |
| Wed 28 Oct | — 20:38 | No data | — |
| Tue 27 Oct | — 20:39 | No data | — |
| Mon 26 Oct | — 20:38 | No data | — |
| Sun 25 Oct | Amsterdam Muiderpoort 20:45 | No data | — |
| Sat 24 Oct | Amsterdam Muiderpoort 20:48 | 0 min | — |
| Fri 23 Oct | — 20:38 | +2 min | +2 min |
| Thu 22 Oct | — 20:39 | No data | — |
| Wed 21 Oct | — 20:38 | No data | — |
| Tue 20 Oct | — 20:38 | 0 min | — |
| Mon 19 Oct | — 20:39 | No data | — |
| Sun 18 Oct | Schiphol Airport 21:15 | +1 min | +2 min |
| Sat 17 Oct | Schiphol Airport 21:16 | 0 min | — |
| Fri 16 Oct | Almere Oostvaarders 20:38 | 0 min | — |
| Thu 15 Oct | — 20:38 | 0 min | — |
| Wed 14 Oct | — 20:38 | No data | — |