Train NS 4651 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 14:23 from Amsterdam Centraal · Thu 5 Nov

Next departure 14:23 today · Amsterdam Centraal
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 8 full · 9 partial · 12 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 10 full · 9 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 7 Oct Max en route +11 min · last fix heading to Almere Buiten +11 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Almere Buiten +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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