Train NS 4658 Almere Oostvaarders – Amsterdam Centraal

Almere Oostvaarders 17:25 → Amsterdam Centraal 18:07 Daily 0 h 42 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:25 from Almere Oostvaarders · Thu 5 Nov

Next departure 17:25 today · Almere Oostvaarders
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 13 full · 2 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 15 full · 2 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Wed 28 Oct Max en route +28 min · last fix heading to Amsterdam Science Park +28 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
17:25on time on time
17:27≈ on time ≈ on time
17:31≈ on time ≈ on time
17:34 / 17:35≈ on time ≈ +1 min
17:38≈ on time ≈ +1 min
17:42≈ on time ≈ +1 min
17:49 / 17:51≈ on time ≈ +1 min
17:56≈ on time ≈ +2 min
17:59≈ on time ≈ +2 min
18:01≈ on time ≈ +2 min
18:07on time +2 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
Wed 4 NovAmsterdam Muiderpoort 18:14No data—
Tue 3 NovAmsterdam Muiderpoort 18:14No data—
Mon 2 NovAmsterdam Muiderpoort 18:14No data—
Sun 1 NovAmsterdam Muiderpoort 18:16Partial coverage0 min—
Sat 31 OctAmsterdam Muiderpoort 18:16+2 min+2 min
Fri 30 OctAmsterdam Muiderpoort 18:16No data—
Thu 29 OctAmsterdam Muiderpoort 18:16No data—
Wed 28 OctAmsterdam Science Park 19:02+28 min+28 min
Tue 27 OctAmsterdam Muiderpoort 18:16No data—
Mon 26 OctAmsterdam Muiderpoort 18:160 min—
Sun 25 OctAlmere Poort 18:41No data—
Sat 24 OctAmsterdam Muiderpoort 18:160 min—
Fri 23 OctAmsterdam Muiderpoort 18:160 min—
Thu 22 OctAmsterdam Muiderpoort 18:120 min—
Wed 21 OctAmsterdam Muiderpoort 18:16No data—
Tue 20 OctAmsterdam Muiderpoort 18:16No data—
Mon 19 OctAmsterdam Muiderpoort 18:160 min—
Sun 18 OctSchiphol Airport 18:460 min—
Sat 17 OctSchiphol Airport 18:47No data—
Fri 16 OctAmsterdam Muiderpoort 18:16No data—
Thu 15 OctAmsterdam Muiderpoort 18:16No data—
Wed 14 OctAmsterdam Muiderpoort 18:16No data—
Tue 13 OctAmsterdam Muiderpoort 18:16No data—
Mon 12 OctAmsterdam Muiderpoort 18:160 min—
Sun 11 OctAmsterdam Muiderpoort 18:17Partial coverage+1 min+2 min
Sat 10 OctAmsterdam Muiderpoort 18:16+1 min—
Fri 9 OctAmsterdam Muiderpoort 18:16+2 min+2 min
Thu 8 OctAmsterdam Muiderpoort 18:160 min—
Wed 7 OctAmsterdam Muiderpoort 18:160 min—
Tue 6 OctAmsterdam Muiderpoort 18:16+3 min+3 min