Train NS 4661 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 16:52 from Amsterdam Centraal · Sun 8 Nov

Next departure 16:52 today · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 13 full · 5 partial · 11 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 18 full · 5 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
16:52on time on time
16:58≈ on time ≈ on time
17:01≈ on time ≈ on time
17:03≈ on time ≈ on time
17:09 / 17:11≈ on time ≈ on time
17:17≈ on time ≈ on time
17:21≈ on time ≈ on time
17:24 / 17:25≈ on time ≈ on time
17:28≈ on time ≈ on time
17:31≈ on time ≈ on time
17: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
Sat 7 NovAlmere Buiten 17:47Partial coverage+1 min+1 min
Fri 6 NovAlmere Buiten 17:440 min—
Thu 5 NovAlmere Buiten 17:440 min—
Wed 4 NovAlmere Buiten 17:44No data—
Tue 3 NovAlmere Buiten 17:44No data—
Mon 2 NovAlmere Buiten 17:390 min—
Sun 1 NovAlmere Buiten 17:46Partial coverage0 min—
Sat 31 OctAlmere Buiten 17:46Partial coverage0 min—
Fri 30 OctAlmere Buiten 17:45No data—
Thu 29 OctAlmere Buiten 17:450 min—
Wed 28 OctAlmere Buiten 17:45No data—
Tue 27 OctAlmere Buiten 17:45No data—
Mon 26 OctAlmere Buiten 17:450 min—
Sun 25 OctAlmere Buiten 17:45No data—
Sat 24 OctAlmere Buiten 17:470 min—
Fri 23 OctAlmere Buiten 18:020 min—
Thu 22 OctAlmere Buiten 17:44No data—
Wed 21 OctAlmere Buiten 17:45No data—
Tue 20 OctAlmere Buiten 17:450 min—
Mon 19 OctAlmere Buiten 17:530 min—
Sun 18 OctDiemen 17:230 min—
Sat 17 OctDiemen 17:240 min—
Fri 16 OctAlmere Buiten 17:460 min—
Thu 15 OctAlmere Buiten 17:45No data—
Wed 14 OctAlmere Buiten 17:50No data—
Tue 13 OctAlmere Buiten 17:45No data—
Mon 12 OctAlmere Buiten 17:450 min—
Sun 11 OctAlmere Buiten 17:46Partial coverage0 min—
Sat 10 OctAlmere Buiten 17:46Partial coverage0 min—
Fri 9 OctAlmere Buiten 17:450 min—