Train NS 4662 Almere Oostvaarders – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Monday 16 November +6 min

Next service: today 18:25 from Almere Oostvaarders · Tue 17 Nov

Next departure 18:25 today · Almere Oostvaarders
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 9 full · 12 partial · 8 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 15 full · 15 partial · 34 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 16 Nov Max en route +6 min · last fix heading to Almere Buiten +6 min
  • Wed 11 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
18:25on time on time
18:27≈ on time ≈ on time
18:31≈ on time ≈ +1 min
18:34 / 18:35≈ on time ≈ +1 min
18:38≈ on time ≈ +1 min
18:42≈ on time ≈ +1 min
18:49 / 18:51≈ +1 min ≈ +2 min
18:56≈ +1 min ≈ +3 min
18:59≈ +1 min ≈ +3 min
19:01≈ +1 min ≈ +3 min
19:07+1 min +3 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 NovAlmere Buiten 20:17+6 min+6 min
Sun 15 NovAmsterdam Muiderpoort 19:18Partial coverage+3 min+3 min
Sat 14 NovAmsterdam Muiderpoort 19:14Partial coverage0 min—
Fri 13 NovDiemen 19:09Partial coverage0 min+3 min
Thu 12 Nov— 19:09+2 min+3 min
Wed 11 Nov— 19:13+5 min+5 min
Tue 10 Nov— 18:39No data—
Mon 9 Nov— 19:090 min—
Sun 8 NovAmsterdam Muiderpoort 19:14Partial coverage+1 min—
Sat 7 NovAmsterdam Muiderpoort 19:14Partial coverage+1 min—
Fri 6 NovAlmere Poort 19:08Partial coverage+1 min—
Thu 5 Nov— 19:080 min—
Wed 4 Nov— 19:09No data—
Tue 3 Nov— 19:09No data—
Mon 2 NovAlmere Centrum 19:08Partial coverage0 min—
Sun 1 NovAmsterdam Muiderpoort 19:14Partial coverage0 min—
Sat 31 OctAmsterdam Muiderpoort 19:16Partial coverage+1 min—
Fri 30 OctWeesp 19:08No data—
Thu 29 Oct— 19:080 min—
Wed 28 Oct— 19:08+1 min+1 min
Tue 27 Oct— 19:090 min—
Mon 26 Oct— 19:08No data—
Sun 25 OctAmsterdam Muiderpoort 19:15No data—
Sat 24 OctAmsterdam Muiderpoort 19:20No data—
Fri 23 OctAmsterdam Muiderpoort 19:15+1 min+1 min
Thu 22 OctAlmere Poort 19:09Partial coverage0 min—
Wed 21 OctAlmere Muziekwijk 19:09No data—
Tue 20 OctAlmere Poort 18:50Partial coverage0 min—
Mon 19 OctAlmere Poort 19:09Partial coverage0 min—
Sun 18 OctSchiphol Airport 19:460 min—