Train NS 4652 Almere Oostvaarders – Amsterdam Centraal

Almere Oostvaarders 15:55 → Amsterdam Centraal 16:37 Daily 0 h 42 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 15:55 from Almere Oostvaarders · Mon 16 Nov

Next departure 15:55 today · Almere Oostvaarders
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 15 full · 2 partial · 11 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 26 full · 2 partial · 53 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: +2 min

Last 30 days

Arrival delay at Amsterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 10 Oct Max en route +15 min · last fix heading to Diemen +15 min
  • Thu 12 Nov Max en route +12 min · last fix heading to Amsterdam Muiderpoort +12 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Amsterdam Muiderpoort +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 4% · 1
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 67% T n=3
  • 100% F n=4
  • 83% S n=6
  • 80% S n=5

Stops and timetable

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

Last 90 days, 28 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
15:55on time on time
15:57≈ on time ≈ on time
16:01≈ on time ≈ on time
16:04 / 16:05≈ on time ≈ +1 min
16:08≈ on time ≈ +1 min
16:12≈ on time ≈ +1 min
16:19 / 16:21≈ on time ≈ +2 min
16:26≈ on time ≈ +2 min
16:28≈ on time ≈ +2 min
16:32≈ on time ≈ +2 min
16:37on time +3 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
Sun 15 NovAmsterdam Muiderpoort 16:44Partial coverage0 min+3 min
Sat 14 NovAmsterdam Muiderpoort 16:49Partial coverage+3 min+6 min
Fri 13 NovAmsterdam Muiderpoort 16:44+1 min—
Thu 12 NovAmsterdam Muiderpoort 16:59+12 min+12 min
Wed 11 NovAmsterdam Muiderpoort 16:440 min—
Mon 9 NovAmsterdam Muiderpoort 16:440 min—
Sun 8 NovAmsterdam Muiderpoort 16:45+1 min—
Sat 7 NovAmsterdam Muiderpoort 16:44+1 min—
Fri 6 NovAlmere Oostvaarders 17:33No data—
Thu 5 NovAmsterdam Muiderpoort 16:44No data—
Wed 4 NovAmsterdam Muiderpoort 16:440 min—
Tue 3 NovAmsterdam Muiderpoort 16:44No data—
Mon 2 NovAmsterdam Muiderpoort 16:44No data—
Sun 1 NovAmsterdam Muiderpoort 16:460 min—
Sat 31 OctAmsterdam Muiderpoort 16:450 min—
Fri 30 OctAmsterdam Muiderpoort 16:46No data—
Thu 29 OctAmsterdam Muiderpoort 16:46No data—
Wed 28 OctAmsterdam Muiderpoort 16:48No data—
Tue 27 OctAmsterdam Muiderpoort 16:460 min—
Mon 26 OctAmsterdam Muiderpoort 16:46No data—
Sun 25 OctAmsterdam Muiderpoort 16:45No data—
Sat 24 OctAmsterdam Muiderpoort 16:450 min—
Fri 23 OctAmsterdam Muiderpoort 16:460 min—
Thu 22 OctAmsterdam Muiderpoort 16:45No data—
Wed 21 OctAmsterdam Muiderpoort 16:47No data—
Tue 20 OctAmsterdam Muiderpoort 16:450 min—
Mon 19 OctAmsterdam Muiderpoort 16:460 min—
Sun 18 OctSchiphol Airport 17:140 min—
Sat 17 OctSchiphol Airport 17:140 min—
Fri 16 OctAmsterdam Muiderpoort 16:460 min—