Train NS 4630 Almere Oostvaarders – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 11:46 No data

  1. Almere Oostvaarders10:25
  2. Almere Parkwijk10:31
  3. Almere Centrum10:34
  4. Almere Poort10:42
  5. Diemen10:56
  6. Amsterdam Science Park10:59
  7. Amsterdam Centraal11:07

Next service: tomorrow 10:25 from Almere Oostvaarders · Sun 18 Oct

Full trip card
Next departure 10:25 tomorrow · Almere Oostvaarders
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 1 full · 6 partial · 20 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 1 full · 6 partial · 62 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 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 11 Oct Max en route +20 min · last fix heading to Almere Poort +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 0% · 0
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
Almere Oostvaarders
10:25
Almere Buiten
10:27
Almere Parkwijk
10:31
Almere Centrum
10:34 / 10:35
Almere Muziekwijk
10:38
Almere Poort
10:42
Weesp
10:49 / 10:51
Diemen
10:56
Amsterdam Science Park
10:59
Amsterdam Muiderpoort
11:01
Amsterdam Centraal
11: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
Sat 17 OctSchiphol Airport 11:46No data—
Fri 16 OctAmsterdam Muiderpoort 11:16No data—
Thu 15 OctAmsterdam Muiderpoort 11:17No data—
Wed 14 OctAmsterdam Muiderpoort 11:33No data—
Tue 13 OctAmsterdam Muiderpoort 11:16No data—
Mon 12 OctAmsterdam Muiderpoort 11:21Partial coverage0 min—
Sun 11 OctAlmere Poort 11:43Partial coverage+17 min+20 min
Sat 10 OctAmsterdam Muiderpoort 11:16Partial coverage0 min—
Fri 9 OctAmsterdam Muiderpoort 11:16+1 min+1 min
Thu 8 OctAmsterdam Muiderpoort 11:16Partial coverage+1 min—
Wed 7 OctAlmere Buiten 12:01Partial coverage0 min—
Tue 6 OctAmsterdam Muiderpoort 11:17Partial coverage+2 min+2 min
Mon 5 OctAmsterdam Science Park 11:13No data—
Fri 2 OctAmsterdam Muiderpoort 11:16No data—
Thu 1 OctAmsterdam Muiderpoort 11:19No data—
Wed 30 SeptAmsterdam Muiderpoort 11:17No data—
Tue 29 SeptAmsterdam Muiderpoort 11:16No data—
Mon 28 SeptAmsterdam Muiderpoort 11:16No data—
Sat 26 SeptAmsterdam Muiderpoort 11:15No data—
Fri 25 SeptAmsterdam Muiderpoort 11:16No data—
Thu 24 SeptAmsterdam Muiderpoort 11:16No data—
Wed 23 SeptAmsterdam Muiderpoort 11:15No data—
Tue 22 SeptAmsterdam Muiderpoort 11:15No data—
Mon 21 SeptAmsterdam Muiderpoort 11:16No data—
Sun 20 SeptAmsterdam Muiderpoort 11:17No data—
Sat 19 SeptAmsterdam Muiderpoort 11:16No data—
Fri 18 SeptAmsterdam Muiderpoort 11:16No data—
Thu 17 SeptAmsterdam Muiderpoort 11:16No data—
Wed 16 SeptAmsterdam Muiderpoort 11:15No data—
Tue 15 SeptAmsterdam Muiderpoort 11:15No data—