Train NS 4644 Almere Oostvaarders – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November +15 min

Next service: today 13:55 from Almere Oostvaarders · Mon 16 Nov

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

  • Sun 15 Nov Max en route +15 min · last fix heading to Weesp +15 min
  • Sat 10 Oct Max en route +6 min · last fix heading to Amsterdam Muiderpoort +6 min
  • Fri 9 Oct Max en route +6 min · last fix heading to Amsterdam Muiderpoort +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 7% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
13:55on time on time
13:57≈ on time ≈ on time
14:01≈ on time ≈ on time
14:04 / 14:05≈ on time ≈ on time
14:08≈ on time ≈ +1 min
14:12≈ on time ≈ +1 min
14:19 / 14:21≈ on time ≈ +1 min
14:26≈ on time ≈ +1 min
14:28≈ on time ≈ +1 min
14:32≈ on time ≈ +2 min
14:37on 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
Sun 15 NovWeesp 15:07Partial coverage+15 min+15 min
Sat 14 NovAmsterdam Muiderpoort 14:44Partial coverage0 min—
Fri 13 NovAmsterdam Muiderpoort 14:440 min—
Thu 12 NovAmsterdam Muiderpoort 14:48+2 min+2 min
Wed 11 NovAmsterdam Muiderpoort 14:44+1 min—
Tue 10 Nov— 14:19No data—
Mon 9 NovAmsterdam Muiderpoort 14:440 min—
Sun 8 NovAmsterdam Muiderpoort 14:44No data—
Sat 7 NovAmsterdam Muiderpoort 14:440 min—
Fri 6 NovAmsterdam Muiderpoort 14:52No data—
Thu 5 NovAmsterdam Muiderpoort 14:440 min—
Wed 4 NovAmsterdam Muiderpoort 14:440 min—
Tue 3 NovAmsterdam Muiderpoort 14:44No data—
Mon 2 NovAmsterdam Muiderpoort 14:440 min—
Sun 1 NovAmsterdam Muiderpoort 14:47+2 min+2 min
Sat 31 OctAmsterdam Muiderpoort 14:450 min—
Fri 30 OctAmsterdam Muiderpoort 14:45No data—
Thu 29 OctAmsterdam Muiderpoort 14:460 min—
Wed 28 OctAmsterdam Muiderpoort 14:45No data—
Tue 27 OctAmsterdam Muiderpoort 14:47No data—
Mon 26 OctAmsterdam Muiderpoort 14:450 min—
Sun 25 OctAmsterdam Muiderpoort 14:46No data—
Sat 24 OctAmsterdam Muiderpoort 14:46+1 min—
Fri 23 OctAlmere Oostvaarders 16:27No data—
Thu 22 OctAmsterdam Muiderpoort 14:46No data—
Wed 21 OctAmsterdam Muiderpoort 14:45No data—
Tue 20 OctAmsterdam Muiderpoort 14:47No data—
Mon 19 OctAmsterdam Muiderpoort 14:460 min—
Sun 18 OctSchiphol Airport 15:170 min—
Sat 17 OctSchiphol Airport 15:140 min—