Train NS 4666 Almere Oostvaarders – Amsterdam Centraal

Almere Oostvaarders 19:25 → Amsterdam Centraal 20:07 Daily 0 h 42 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 19:25 from Almere Oostvaarders · Thu 5 Nov

Next departure 19:25 today · Almere Oostvaarders
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 10 full · 4 partial · 13 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 12 full · 4 partial · 26 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

16 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 67% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 stops).

Last 90 days, 16 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.

StopSched.Usually 9 days in 10
19:25on time on time
19:27≈ on time ≈ on time
19:31≈ on time ≈ on time
19:34 / 19:35≈ on time ≈ on time
19:38≈ on time ≈ +1 min
19:42≈ on time ≈ +1 min
19:49 / 19:51≈ on time ≈ +1 min
19:56≈ on time ≈ +1 min
19:59≈ +1 min ≈ +1 min
20:01≈ +1 min ≈ +1 min
20:07+1 min +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

DateLast stopFinalMax
Wed 4 Nov— 20:08+1 min—
Sun 1 NovAmsterdam Muiderpoort 20:14Partial coverage+1 min—
Sat 31 OctAmsterdam Muiderpoort 20:15Partial coverage0 min—
Fri 30 Oct— 20:08No data—
Thu 29 Oct— 20:08+2 min+2 min
Wed 28 Oct— 20:08No data—
Tue 27 Oct— 20:18No data—
Mon 26 OctWeesp 20:08No data—
Sun 25 OctAmsterdam Muiderpoort 20:18No data—
Sat 24 OctAmsterdam Muiderpoort 20:16No data—
Fri 23 OctAlmere Buiten 19:410 min—
Thu 22 Oct— 20:090 min—
Wed 21 Oct— 20:090 min—
Tue 20 Oct— 20:09No data—
Mon 19 Oct— 20:13No data—
Sun 18 OctSchiphol Airport 20:47+1 min+2 min
Sat 17 OctSchiphol Airport 20:46No data—
Fri 16 OctWeesp 20:08No data—
Thu 15 Oct— 20:08No data—
Wed 14 OctAlmere Poort 20:08No data—
Tue 13 Oct— 20:09No data—
Mon 12 Oct— 20:080 min—
Sun 11 OctAmsterdam Muiderpoort 20:18Partial coverage+2 min+3 min
Sat 10 OctAmsterdam Muiderpoort 20:16Partial coverage+1 min—
Fri 9 Oct— 20:08+1 min—
Thu 8 Oct— 20:090 min—
Wed 7 Oct— 20:11+4 min+4 min
Tue 6 Oct— 20:080 min—
Mon 5 Oct— 20:03+1 min+2 min
Sat 26 SeptAmsterdam Muiderpoort 20:15No data—