Train NS 4635 Amsterdam Centraal – Almere Oostvaarders

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 10:23 from Amsterdam Centraal · Tue 10 Nov

Next departure 10:23 today · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 11 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 13 full · 11 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Almere Oostvaarders, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
10:23on time on time
10:28≈ on time ≈ on time
10:31≈ on time ≈ on time
10:34≈ on time ≈ on time
10:39 / 10:41≈ on time ≈ on time
10:47≈ on time ≈ on time
10:51≈ on time ≈ on time
10:54 / 10:55≈ on time ≈ on time
10:58≈ on time ≈ on time
11:01≈ on time ≈ on time
11:05on time on time

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 9 NovAlmere Buiten 11:14Partial coverage0 min—
Sun 8 NovAlmere Buiten 11:140 min—
Sat 7 NovAlmere Buiten 11:140 min—
Fri 6 NovAlmere Buiten 11:14No data—
Thu 5 NovAlmere Buiten 11:14No data—
Wed 4 NovAlmere Buiten 11:14Partial coverage0 min—
Tue 3 NovAlmere Buiten 11:14No data—
Mon 2 NovAlmere Buiten 11:14No data—
Sun 1 NovAlmere Buiten 11:170 min—
Sat 31 OctAlmere Buiten 11:160 min—
Fri 30 OctAlmere Buiten 11:160 min—
Thu 29 OctAlmere Buiten 11:17Partial coverage0 min—
Wed 28 OctAlmere Buiten 11:16Partial coverage0 min—
Tue 27 OctAlmere Buiten 11:16Partial coverage0 min—
Mon 26 OctAlmere Buiten 11:16No data—
Sun 25 OctAlmere Buiten 11:16No data—
Sat 24 OctAlmere Buiten 11:170 min—
Fri 23 OctAlmere Buiten 11:180 min—
Thu 22 OctAlmere Buiten 11:18No data—
Wed 21 OctAlmere Buiten 11:16Partial coverage0 min—
Tue 20 OctAlmere Buiten 11:16Partial coverage0 min—
Mon 19 OctAlmere Buiten 11:22No data—
Sun 18 OctDiemen 11:070 min+15 min
Sat 17 OctDiemen 10:520 min—
Fri 16 OctAlmere Buiten 11:160 min—
Thu 15 OctAlmere Buiten 11:16No data—
Wed 14 OctAlmere Buiten 11:16Partial coverage0 min—
Tue 13 OctAlmere Buiten 11:16No data—
Mon 12 OctAlmere Buiten 11:22No data—
Sun 11 OctAlmere Buiten 11:160 min—