Train NS 4626 Almere Oostvaarders – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Muiderpoort at 10:17 No data

  1. Almere Oostvaarders09:25
  2. Almere Parkwijk09:31
  3. Almere Centrum09:34
  4. Almere Poort09:42
  5. Diemen09:56
  6. Amsterdam Muiderpoort10:01
  7. Amsterdam Centraal10:07

Next service: tomorrow 09:25 from Almere Oostvaarders · Wed 21 Oct

Full trip card
Next departure 09:25 tomorrow · Almere Oostvaarders
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 2 full · 7 partial · 17 no data
On-time · 90 days
67%
6/9 runs under 3 min
RT coverage: 2 full · 7 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Sun 18 Oct Max en route +12 min · last fix heading to Schiphol Airport +11 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Amsterdam Muiderpoort +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Amsterdam Muiderpoort +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 6
  • 3–10 min 22% · 2
  • 10–30 min 11% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
Almere Oostvaarders
09:25
Almere Buiten
09:27
Almere Parkwijk
09:31
Almere Centrum
09:34 / 09:35
Almere Muziekwijk
09:38
Almere Poort
09:42
Weesp
09:49 / 09:51
Diemen
09:56
Amsterdam Science Park
09:59
Amsterdam Muiderpoort
10:01
Amsterdam Centraal
10:07

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.

Recent runs

DateLast stopFinalMax
Tue 20 OctAmsterdam Muiderpoort 10:17No data—
Mon 19 OctAmsterdam Muiderpoort 10:16Partial coverage0 min—
Sun 18 OctSchiphol Airport 10:58+11 min+12 min
Sat 17 OctSchiphol Airport 10:460 min—
Fri 16 OctAmsterdam Muiderpoort 10:16No data—
Thu 15 OctAlmere Parkwijk 10:58No data—
Wed 14 OctAmsterdam Muiderpoort 10:16No data—
Tue 13 OctAmsterdam Muiderpoort 10:16No data—
Mon 12 OctAmsterdam Muiderpoort 10:16Partial coverage0 min—
Sat 10 OctAmsterdam Muiderpoort 10:20Partial coverage+5 min+5 min
Fri 9 OctAmsterdam Muiderpoort 10:19Partial coverage+4 min+4 min
Thu 8 OctAmsterdam Muiderpoort 10:16Partial coverage+1 min—
Wed 7 OctAmsterdam Muiderpoort 10:17Partial coverage0 min—
Tue 6 OctAmsterdam Muiderpoort 10:15Partial coverage0 min—
Mon 5 OctAmsterdam Science Park 10:13No data—
Fri 2 OctAmsterdam Muiderpoort 10:16No data—
Thu 1 OctAmsterdam Muiderpoort 10:15No data—
Wed 30 SeptAmsterdam Muiderpoort 10:17No data—
Tue 29 SeptAmsterdam Muiderpoort 10:16No data—
Mon 28 SeptAmsterdam Muiderpoort 10:15No data—
Sat 26 SeptAmsterdam Muiderpoort 10:15No data—
Fri 25 SeptAmsterdam Muiderpoort 10:16No data—
Thu 24 SeptAmsterdam Muiderpoort 10:15No data—
Wed 23 SeptAmsterdam Muiderpoort 10:16No data—
Tue 22 SeptAmsterdam Muiderpoort 10:16No data—
Mon 21 SeptAmsterdam Muiderpoort 10:16No data—
Sat 19 SeptAmsterdam Muiderpoort 10:16No data—
Fri 18 SeptAmsterdam Muiderpoort 10:16No data—
Thu 17 SeptAmsterdam Muiderpoort 10:16No data—
Wed 16 SeptAmsterdam Muiderpoort 10:17No data—