Train NS 4665 Amsterdam Centraal – Almere Oostvaarders

Amsterdam Centraal 17:52 → Almere Oostvaarders 18:35 Daily 0 h 43 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:52 from Amsterdam Centraal · Fri 6 Nov

Next departure 17:52 today · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 7 full · 12 partial · 10 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 8 full · 14 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 26 Oct Max en route +4 min · last fix heading to Diemen +4 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

  • 80% M n=5
  • 100% T n=3
  • 100% W n=1
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

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
17:52on time on time
17:58≈ on time ≈ on time
18:01≈ on time ≈ on time
18:03≈ on time ≈ on time
18:09 / 18:11≈ on time ≈ on time
18:17≈ on time ≈ on time
18:21≈ on time ≈ on time
18:24 / 18:25≈ on time ≈ on time
18:28≈ on time ≈ on time
18:31≈ on time ≈ on time
18:35on time on time

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
Thu 5 NovWeesp 18:39No data—
Wed 4 NovWeesp 18:37No data—
Tue 3 NovWeesp 18:34No data—
Mon 2 NovDiemen 18:43Partial coverage+2 min+3 min
Sun 1 NovAlmere Buiten 18:48Partial coverage+2 min+3 min
Sat 31 OctAlmere Buiten 18:48Partial coverage+2 min+2 min
Fri 30 OctAlmere Buiten 18:45Partial coverage0 min—
Thu 29 OctAmsterdam Science Park 18:380 min—
Wed 28 OctAmsterdam Centraal 18:36No data—
Tue 27 OctDiemen 18:41No data—
Mon 26 OctDiemen 18:52Partial coverage+4 min+4 min
Sun 25 OctAlmere Buiten 18:45No data—
Sat 24 OctAlmere Buiten 18:510 min—
Fri 23 OctAlmere Buiten 18:46No data—
Thu 22 OctAlmere Centrum 19:15Partial coverage0 min—
Wed 21 OctAlmere Buiten 18:45No data—
Tue 20 OctAlmere Buiten 18:45Partial coverage0 min—
Mon 19 OctAlmere Buiten 18:45Partial coverage0 min—
Sun 18 OctDiemen 18:23+1 min—
Sat 17 OctDiemen 18:260 min—
Fri 16 OctAlmere Buiten 18:480 min—
Thu 15 OctAlmere Parkwijk 18:42No data—
Wed 14 OctAlmere Buiten 18:42No data—
Tue 13 OctAlmere Buiten 18:460 min—
Mon 12 OctAlmere Buiten 18:480 min—
Sun 11 OctAlmere Buiten 18:46Partial coverage0 min+1 min
Sat 10 OctAlmere Buiten 18:48Partial coverage+2 min+2 min
Fri 9 OctAlmere Buiten 18:45Partial coverage0 min—
Thu 8 OctDiemen 18:37Partial coverage0 min+1 min
Wed 7 OctDiemen 18:36Partial coverage0 min—