Train NS 4657 Amsterdam Centraal – Almere Oostvaarders

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

✓ Today’s run finished

Today, last fix heading to Almere Buiten at 16:44 0 min

  1. Amsterdam Centraal15:52
  2. Amsterdam Science Park16:01
  3. Diemen16:03
  4. Almere Poort16:17
  5. Almere Centrum16:24
  6. Almere Buiten16:31
  7. Almere Oostvaarders16:35

Next service: tomorrow 15:52 from Amsterdam Centraal · Fri 6 Nov

Next departure 15:52 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 8 full · 11 partial · 11 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 9 full · 12 partial · 53 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

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

  • Early 0% · 0
  • On time 100% · 21
  • 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=3
  • 100% T n=2
  • 100% F n=3
  • 100% S n=4
  • 100% S n=2

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
15:52on time on time
15:58≈ on time ≈ on time
16:01≈ on time ≈ on time
16:03≈ on time ≈ on time
16:09 / 16:11≈ on time ≈ on time
16:17≈ on time ≈ +1 min
16:21≈ on time ≈ +1 min
16:24 / 16:25≈ on time ≈ +1 min
16:28≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:35on 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
Thu 5 NovAlmere Buiten 16:44Partial coverage0 min—
Wed 4 NovAlmere Buiten 16:44Partial coverage0 min—
Tue 3 NovAlmere Buiten 16:44No data—
Mon 2 NovAlmere Buiten 16:44Partial coverage0 min—
Sun 1 NovAmsterdam Centraal 16:07No data—
Sat 31 OctAlmere Buiten 16:460 min—
Fri 30 OctAlmere Buiten 16:48No data—
Thu 29 OctAlmere Buiten 16:45No data—
Wed 28 OctAlmere Buiten 16:46No data—
Tue 27 OctAlmere Buiten 16:47No data—
Mon 26 OctAlmere Buiten 16:46Partial coverage0 min—
Sun 25 OctAlmere Buiten 16:46No data—
Sat 24 OctAlmere Buiten 16:470 min+1 min
Fri 23 OctAlmere Buiten 16:470 min—
Thu 22 OctAlmere Buiten 16:45No data—
Wed 21 OctAlmere Buiten 16:45Partial coverage0 min—
Tue 20 OctAlmere Buiten 16:46Partial coverage0 min—
Mon 19 OctAlmere Buiten 16:46Partial coverage0 min—
Sun 18 OctDiemen 16:25+3 min+3 min
Sat 17 OctDiemen 16:220 min—
Fri 16 OctAlmere Buiten 16:460 min—
Thu 15 OctAlmere Buiten 16:46No data—
Wed 14 OctAlmere Buiten 16:46No data—
Tue 13 OctAlmere Buiten 16:47No data—
Mon 12 OctAlmere Buiten 16:47+1 min+3 min
Sun 11 OctAlmere Buiten 16:46Partial coverage0 min—
Sat 10 OctAlmere Buiten 16:460 min+3 min
Fri 9 OctAlmere Buiten 16:46Partial coverage0 min—
Thu 8 OctAlmere Buiten 16:46Partial coverage0 min—
Wed 7 OctAlmere Buiten 16:45Partial coverage0 min—