Train NS 4645 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Sunday 8 November No data

Next service: today 12:52 from Amsterdam Centraal · Mon 9 Nov

Next departure 12:52 today · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 5 full · 13 partial · 11 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 6 full · 18 partial · 54 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
12:52on time on time
12:58≈ on time ≈ on time
13:01≈ on time ≈ on time
13:03≈ on time ≈ on time
13:09 / 13:11≈ on time ≈ on time
13:17≈ on time ≈ on time
13:21≈ on time ≈ on time
13:24 / 13:25≈ on time ≈ on time
13:28≈ on time ≈ on time
13:31≈ on time ≈ on time
13:35on time on time

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 8 NovAlmere Buiten 13:44Partial coverageNo data—
Sat 7 NovAlmere Buiten 13:44Partial coverage+1 min—
Fri 6 NovAlmere Buiten 13:44No data—
Thu 5 NovAlmere Buiten 13:44Partial coverage0 min—
Wed 4 NovAlmere Buiten 13:44Partial coverage+1 min—
Tue 3 NovAlmere Buiten 13:44No data—
Mon 2 NovAlmere Buiten 13:44Partial coverage0 min—
Sun 1 NovAlmere Buiten 13:470 min+1 min
Sat 31 OctAlmere Buiten 13:46Partial coverage+1 min—
Fri 30 OctAlmere Buiten 13:46No data—
Thu 29 OctAlmere Buiten 13:46Partial coverage0 min—
Wed 28 OctAlmere Buiten 13:47Partial coverage0 min—
Tue 27 OctAlmere Buiten 13:46Partial coverage0 min—
Mon 26 OctAlmere Buiten 13:45Partial coverage0 min—
Sun 25 OctAlmere Buiten 13:46No data—
Sat 24 OctAlmere Buiten 13:520 min—
Fri 23 OctAlmere Buiten 13:590 min—
Thu 22 OctAlmere Buiten 13:46Partial coverage0 min—
Wed 21 OctAlmere Buiten 13:50No data—
Tue 20 OctAlmere Buiten 13:46Partial coverage0 min—
Mon 19 OctAlmere Buiten 13:46Partial coverage0 min—
Sun 18 OctDiemen 13:230 min—
Sat 17 OctDiemen 13:260 min—
Fri 16 OctAlmere Buiten 13:46No data—
Thu 15 OctAlmere Buiten 13:45No data—
Wed 14 OctAlmere Buiten 13:46No data—
Tue 13 OctAlmere Buiten 13:46No data—
Mon 12 OctAlmere Buiten 13:45No data—
Sun 11 OctAlmere Buiten 13:46Partial coverage0 min—
Sat 10 OctAlmere Buiten 13:46Partial coverage0 min—