Train NS 4655 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

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

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

  • Sun 18 Oct Max en route +7 min · last fix heading to Diemen +7 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 67% S n=3

Stops and timetable

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

Last 90 days, 22 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:23on time on time
15:28— —
15:31— —
15:34— —
15:39 / 15:41— —
15:47— —
15:51— —
15:54 / 15:55— —
15:58— —
16:01— —
16:05— —

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 16:17Partial coverage+1 min+1 min
Tue 3 NovAlmere Buiten 16:14No data—
Mon 2 NovAlmere Buiten 16:14No data—
Sun 1 NovAlmere Buiten 16:16Partial coverage0 min—
Sat 31 OctAlmere Buiten 16:15Partial coverage0 min—
Fri 30 OctAlmere Buiten 16:16Partial coverage0 min—
Thu 29 OctAlmere Buiten 16:16Partial coverage0 min—
Wed 28 OctAlmere Buiten 16:16No data—
Tue 27 OctAlmere Buiten 16:16Partial coverage0 min—
Mon 26 OctAlmere Buiten 16:16No data—
Sun 25 OctAlmere Buiten 16:19No data—
Sat 24 OctAlmere Buiten 16:170 min—
Fri 23 OctAlmere Buiten 16:17No data—
Thu 22 OctAlmere Buiten 16:41Partial coverage0 min—
Wed 21 OctAlmere Buiten 16:19No data—
Tue 20 OctAlmere Buiten 16:17Partial coverage0 min—
Mon 19 OctAlmere Buiten 16:16Partial coverage0 min—
Sun 18 OctDiemen 15:59+7 min+7 min
Sat 17 OctDiemen 15:520 min—
Fri 16 OctAlmere Buiten 16:16Partial coverage0 min—
Thu 15 OctAlmere Buiten 16:16No data—
Wed 14 OctAlmere Buiten 16:16Partial coverage0 min—
Tue 13 OctAlmere Buiten 16:17No data—
Mon 12 OctAlmere Buiten 16:16Partial coverage0 min—
Sun 11 OctAlmere Buiten 16:16Partial coverage+1 min—
Sat 10 OctAlmere Buiten 16:15Partial coverage0 min—
Fri 9 OctAlmere Buiten 16:16Partial coverage0 min—
Thu 8 OctAlmere Buiten 16:16Partial coverage0 min—
Wed 7 OctAlmere Buiten 16:16Partial coverage+1 min+1 min
Tue 6 OctAlmere Buiten 16:16Partial coverage0 min+1 min