Train NS 4616 Almere Oostvaarders – Amsterdam Centraal

Almere Oostvaarders 06:55 → Amsterdam Centraal 07:37 Mon, Tue, Wed, Thu, Fri 0 h 42 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 06:55 from Almere Oostvaarders · Tue 17 Nov

Next departure 06:55 today · Almere Oostvaarders
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 16 full · 1 partial · 3 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 27 full · 1 partial · 36 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: +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

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 100% · 28
  • 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=5
  • 100% W n=5
  • 100% T n=6
  • 100% F n=5
  • 100% S n=1
  • 100% S n=1

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
06:55on time on time
06:57≈ on time ≈ on time
07:01≈ on time ≈ on time
07:04 / 07:05≈ on time ≈ on time
07:08≈ on time ≈ on time
07:12≈ on time ≈ on time
07:19 / 07:21≈ on time ≈ on time
07:26≈ on time ≈ on time
07:29≈ on time ≈ on time
07:32≈ on time ≈ +1 min
07:37on 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
Mon 16 NovAmsterdam Muiderpoort 07:44Partial coverage+1 min+1 min
Fri 13 NovAmsterdam Muiderpoort 07:48+3 min+3 min
Thu 12 NovAmsterdam Muiderpoort 07:440 min—
Wed 11 NovAmsterdam Muiderpoort 07:440 min—
Mon 9 NovAmsterdam Muiderpoort 07:440 min—
Fri 6 NovAmsterdam Muiderpoort 07:44No data—
Thu 5 NovAmsterdam Muiderpoort 07:440 min—
Wed 4 NovAmsterdam Muiderpoort 07:48+2 min+3 min
Tue 3 NovAmsterdam Muiderpoort 07:470 min—
Mon 2 NovAmsterdam Muiderpoort 07:44No data—
Fri 30 OctAmsterdam Muiderpoort 07:450 min—
Thu 29 OctAmsterdam Muiderpoort 07:46+1 min+3 min
Wed 28 OctAlmere Poort 07:39No data—
Tue 27 OctAmsterdam Muiderpoort 07:460 min—
Mon 26 OctAmsterdam Muiderpoort 07:46+1 min—
Fri 23 OctAmsterdam Muiderpoort 07:450 min—
Thu 22 OctAmsterdam Muiderpoort 07:460 min—
Wed 21 OctAmsterdam Muiderpoort 07:460 min—
Tue 20 OctAmsterdam Muiderpoort 07:460 min—
Mon 19 OctAmsterdam Muiderpoort 07:460 min—
Sun 18 OctAmsterdam Muiderpoort 07:460 min—
Sat 17 OctAmsterdam Muiderpoort 07:460 min—
Fri 16 OctAmsterdam Muiderpoort 07:460 min—
Thu 15 OctAmsterdam Muiderpoort 07:460 min—
Wed 14 OctAmsterdam Muiderpoort 07:480 min—
Tue 13 OctAmsterdam Muiderpoort 07:460 min—
Mon 12 OctAmsterdam Muiderpoort 07:450 min—
Fri 9 OctAmsterdam Muiderpoort 07:460 min—
Thu 8 OctAmsterdam Muiderpoort 07:460 min—
Wed 7 OctAmsterdam Muiderpoort 07:460 min—