Train NS 4675 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 20:23 from Amsterdam Centraal · Sat 14 Nov

Next departure 20:23 today · Amsterdam Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 15 full · 3 partial · 10 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 21 full · 4 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Mon 9 Nov Max en route +22 min · last fix heading to — +21 min
  • Sat 10 Oct Max en route +11 min · last fix heading to Almere Buiten +10 min
  • Fri 16 Oct Max en route +8 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 4% · 1
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 80% F n=5
  • 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, 25 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
20:23on time +1 min
20:28≈ on time ≈ +1 min
20:31≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:39 / 20:41≈ on time ≈ +1 min
20:47≈ on time ≈ +1 min
20:51≈ on time ≈ +1 min
20:54 / 20:55≈ on time ≈ +1 min
20:58≈ on time ≈ +1 min
21:01≈ on time ≈ +1 min
21: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
Fri 13 Nov— 21:040 min—
Thu 12 Nov— 21:040 min—
Wed 11 Nov— 21:24No data—
Tue 10 Nov— 21:04No data—
Mon 9 Nov— 21:49+21 min+22 min
Sun 8 NovAlmere Buiten 21:14Partial coverage0 min—
Sat 7 NovAlmere Buiten 21:14Partial coverage0 min—
Fri 6 Nov— 21:04+1 min+1 min
Thu 5 Nov— 21:04No data—
Wed 4 Nov— 21:09+1 min+2 min
Tue 3 Nov— 21:05No data—
Mon 2 Nov— 21:04No data—
Sun 1 NovAlmere Buiten 21:14Partial coverage0 min—
Sat 31 OctAlmere Buiten 21:16No data—
Thu 29 Oct— 21:070 min—
Wed 28 Oct— 21:06No data—
Tue 27 Oct— 21:07No data—
Mon 26 Oct— 21:060 min—
Sun 25 OctAlmere Buiten 21:15No data—
Sat 24 OctAlmere Centrum 21:390 min—
Fri 23 Oct— 21:080 min+1 min
Thu 22 Oct— 21:070 min—
Wed 21 Oct— 21:070 min—
Tue 20 Oct— 21:070 min—
Mon 19 Oct— 21:110 min—
Sun 18 OctDiemen 20:520 min—
Sat 17 OctDiemen 20:58No data—
Fri 16 Oct— 21:23+7 min+8 min
Thu 15 Oct— 21:06No data—
Wed 14 Oct— 03:25No data—