Train NS 4667 Amsterdam Centraal – Almere Oostvaarders

Amsterdam Centraal 18:23 → Almere Oostvaarders 19:05 Daily 0 h 42 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 18:23 from Amsterdam Centraal · Mon 9 Nov

Next departure 18:23 today · Amsterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 12 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 14 full · 8 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

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

  • Mon 2 Nov Max en route +8 min · last fix heading to Amsterdam Muiderpoort +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
18:23on time on time
18:28≈ on time ≈ on time
18:31≈ on time ≈ on time
18:34≈ on time ≈ on time
18:39 / 18:41≈ on time ≈ +1 min
18:47≈ on time ≈ +1 min
18:51≈ on time ≈ +1 min
18:54 / 18:55≈ on time ≈ +1 min
18:58≈ on time ≈ +1 min
19:01≈ on time ≈ +1 min
19:05on time +1 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
Sun 8 NovAlmere Buiten 19:14Partial coverage0 min—
Sat 7 NovAlmere Buiten 19:17+1 min+1 min
Fri 6 NovAlmere Poort 19:04Partial coverage0 min—
Thu 5 Nov— 19:040 min—
Wed 4 Nov— 19:190 min—
Tue 3 Nov— 19:09No data—
Mon 2 NovAmsterdam Muiderpoort 19:24Partial coverage+8 min+8 min
Sun 1 NovAlmere Buiten 19:14Partial coverage0 min—
Sat 31 OctAlmere Buiten 19:160 min—
Fri 30 OctAlmere Muziekwijk 19:07Partial coverage0 min—
Thu 29 Oct— 18:39No data—
Wed 28 Oct— 19:22+1 min+1 min
Tue 27 Oct— 19:070 min—
Mon 26 Oct— 19:06No data—
Sun 25 OctAlmere Buiten 19:21No data—
Sat 24 OctAlmere Buiten 19:180 min—
Fri 23 OctAlmere Buiten 19:15+1 min+2 min
Thu 22 OctWeesp 19:11No data—
Wed 21 OctDiemen 19:07No data—
Tue 20 OctWeesp 19:09No data—
Mon 19 OctWeesp 19:11No data—
Sun 18 OctDiemen 18:53+1 min+1 min
Sat 17 OctDiemen 18:54No data—
Fri 16 OctAlmere Buiten 19:15Partial coverage0 min—
Thu 15 OctAmsterdam Muiderpoort 19:08No data—
Wed 14 OctAlmere Buiten 19:15No data—
Tue 13 OctDiemen 19:11No data—
Mon 12 OctWeesp 19:070 min—
Sun 11 OctAlmere Buiten 19:16Partial coverage0 min—
Sat 10 OctAlmere Buiten 19:160 min—