Train NS 4656 Almere Oostvaarders – Amsterdam Centraal

Almere Oostvaarders 16:55 → Amsterdam Centraal 17:37 Daily 0 h 42 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Almere Oostvaarders16:55
  2. Almere Parkwijk17:01
  3. Almere Centrum17:04
  4. Almere Poort17:12
  5. Diemen17:26
  6. Amsterdam Muiderpoort17:31
  7. Amsterdam Centraal17:37

Next service: tomorrow 16:55 from Almere Oostvaarders · Fri 23 Oct

Full trip card
Next departure 16:55 tomorrow · Almere Oostvaarders
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 13 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 55 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
Almere Oostvaarders
16:55
Almere Buiten
16:57
Almere Parkwijk
17:01
Almere Centrum
17:04 / 17:05
Almere Muziekwijk
17:08
Almere Poort
17:12
Weesp
17:19 / 17:21
Diemen
17:26
Amsterdam Science Park
17:28
Amsterdam Muiderpoort
17:31
Amsterdam Centraal
17:37

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
Thu 22 OctAmsterdam Muiderpoort 17:44No data—
Wed 21 OctAmsterdam Muiderpoort 17:45Partial coverage0 min—
Tue 20 OctAmsterdam Muiderpoort 17:45Partial coverage0 min—
Mon 19 OctAmsterdam Muiderpoort 17:45Partial coverage0 min—
Sun 18 OctSchiphol Airport 18:150 min—
Sat 17 OctSchiphol Airport 18:15No data—
Fri 16 OctAmsterdam Muiderpoort 17:46Partial coverage0 min—
Thu 15 OctAmsterdam Muiderpoort 17:450 min—
Wed 14 OctAmsterdam Muiderpoort 17:46No data—
Tue 13 OctAmsterdam Muiderpoort 17:45No data—
Mon 12 OctAmsterdam Muiderpoort 17:450 min—
Sun 11 OctAmsterdam Muiderpoort 17:46Partial coverage+1 min—
Sat 10 OctAmsterdam Muiderpoort 17:46Partial coverage+2 min+2 min
Fri 9 OctAmsterdam Muiderpoort 17:45Partial coverage+1 min—
Thu 8 OctAmsterdam Muiderpoort 17:45Partial coverage+1 min—
Wed 7 OctAmsterdam Muiderpoort 17:450 min—
Tue 6 OctAmsterdam Muiderpoort 17:45Partial coverage+2 min+4 min
Mon 5 OctAmsterdam Science Park 17:420 min—
Fri 2 OctAmsterdam Muiderpoort 17:45No data—
Thu 1 OctAmsterdam Muiderpoort 17:45No data—
Wed 30 SeptAmsterdam Muiderpoort 17:45No data—
Tue 29 SeptAmsterdam Muiderpoort 17:45No data—
Mon 28 SeptAmsterdam Muiderpoort 17:45No data—
Sat 26 SeptAmsterdam Muiderpoort 17:44No data—
Fri 25 SeptAmsterdam Muiderpoort 17:45No data—
Thu 24 SeptAmsterdam Muiderpoort 17:45No data—
Wed 23 SeptAmsterdam Muiderpoort 17:45No data—
Tue 22 SeptAmsterdam Muiderpoort 17:45No data—
Mon 21 SeptAmsterdam Muiderpoort 17:45No data—
Sun 20 SeptAmsterdam Muiderpoort 17:45No data—