Train NS 4671 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Wednesday 4 November +21 min

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

Next departure 19:23 today · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 14 full · 5 partial · 9 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 16 full · 5 partial · 22 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: 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

Worst days

  • Wed 4 Nov Max en route +22 min · last fix heading to — +21 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 67% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% 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, 21 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:23on time on time
19:28≈ on time ≈ on time
19:31≈ on time ≈ on time
19:34≈ on time ≈ on time
19:39 / 19:41≈ on time ≈ on time
19:47≈ on time ≈ +1 min
19:51≈ on time ≈ +1 min
19:54 / 19:55≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20:01≈ on time ≈ +1 min
20: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
Wed 4 Nov— 20:49+21 min+22 min
Mon 2 Nov— 20:04No data—
Sun 1 NovAlmere Buiten 20:14Partial coverage0 min—
Sat 31 OctAlmere Buiten 20:17Partial coverage0 min+1 min
Fri 30 Oct— 20:060 min—
Thu 29 Oct— 20:060 min—
Wed 28 Oct— 20:07No data—
Tue 27 Oct— 20:07No data—
Mon 26 OctAlmere Muziekwijk 20:04No data—
Sun 25 OctAlmere Buiten 20:16No data—
Sat 24 OctAlmere Buiten 20:190 min—
Fri 23 OctAmsterdam Centraal 20:070 min—
Thu 22 Oct— 20:070 min—
Wed 21 Oct— 20:19No data—
Tue 20 Oct— 20:090 min—
Mon 19 Oct— 20:250 min—
Sun 18 OctDiemen 19:54+1 min+1 min
Sat 17 OctDiemen 19:53No data—
Fri 16 OctAlmere Centrum 20:11No data—
Thu 15 Oct— 20:08No data—
Wed 14 OctAlmere Poort 20:07Partial coverage0 min—
Tue 13 Oct— 02:250 min—
Mon 12 Oct— 20:070 min—
Sun 11 OctAlmere Buiten 20:16Partial coverage0 min—
Sat 10 OctAlmere Buiten 20:16Partial coverage0 min—
Fri 9 Oct— 20:060 min—
Thu 8 Oct— 02:250 min—
Wed 7 Oct— 20:060 min—
Tue 6 Oct— 20:060 min—
Mon 5 Oct— 20:07+1 min—