Train NS 4647 Amsterdam Centraal – Almere Oostvaarders

Amsterdam Centraal 13:22 → Almere Oostvaarders 14:05 Daily 0 h 43 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 13:22 from Amsterdam Centraal · Sat 7 Nov

Next departure 13:22 today · Amsterdam Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 8 full · 8 partial · 13 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 55 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
13:22on time on time
13:28≈ on time ≈ +1 min
13:31≈ on time ≈ +1 min
13:34≈ on time ≈ on time
13:39 / 13:41≈ on time ≈ on time
13:47≈ on time ≈ on time
13:51≈ on time ≈ on time
13:54 / 13:55≈ on time ≈ on time
13:58≈ on time ≈ on time
14:01≈ on time ≈ on time
14:05on 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
Fri 6 NovAlmere Buiten 14:14No data—
Thu 5 NovAlmere Buiten 14:22No data—
Wed 4 NovAlmere Buiten 14:18Partial coverage+2 min+2 min
Tue 3 NovAlmere Buiten 14:22No data—
Mon 2 NovAlmere Buiten 14:14No data—
Sun 1 NovAlmere Buiten 14:170 min+1 min
Sat 31 OctAlmere Buiten 14:160 min—
Fri 30 OctAlmere Buiten 14:16No data—
Thu 29 OctAlmere Buiten 14:16Partial coverage0 min—
Wed 28 OctAlmere Buiten 14:16Partial coverage0 min—
Tue 27 OctAlmere Buiten 14:16Partial coverage0 min—
Mon 26 OctAlmere Buiten 14:21No data—
Sun 25 OctAlmere Buiten 14:17No data—
Sat 24 OctAlmere Buiten 14:220 min—
Fri 23 OctAlmere Buiten 14:210 min—
Thu 22 OctAlmere Buiten 14:16Partial coverage0 min—
Wed 21 OctAlmere Buiten 14:16No data—
Tue 20 OctAlmere Buiten 14:16No data—
Mon 19 OctAlmere Buiten 14:16Partial coverage0 min—
Sun 18 OctDiemen 13:53+1 min—
Sat 17 OctDiemen 13:550 min—
Fri 16 OctAmsterdam Centraal 14:31No data—
Thu 15 OctAlmere Buiten 14:15No data—
Wed 14 OctAlmere Buiten 14:17No data—
Tue 13 OctAlmere Buiten 14:16No data—
Mon 12 OctAlmere Buiten 14:16Partial coverage0 min—
Sun 11 OctAlmere Buiten 14:160 min—
Sat 10 OctAlmere Buiten 14:150 min+2 min
Fri 9 OctAlmere Buiten 14:18Partial coverage+2 min+2 min
Thu 8 OctAlmere Buiten 14:16Partial coverage0 min—