Train NS 2668 Almere Centrum – Amsterdam Centraal

Almere Centrum 20:01 → Amsterdam Centraal 20:22 Daily 0 h 21 min · 2 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 20:01 from Almere Centrum · Sat 7 Nov

Next departure 20:01 today · Almere Centrum
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 13 full · 0 partial · 14 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 20 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 10 Oct Max en route +7 min · last fix heading to Almere Centrum +7 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
20:01on time +2 min
20:22+1 min +3 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
Fri 6 Nov— 20:23+1 min+1 min
Thu 5 Nov— 20:24No data—
Wed 4 Nov— 20:240 min—
Tue 3 Nov— 20:23No data—
Mon 2 Nov— 20:23No data—
Sun 1 NovAlmere Centrum 20:24+1 min—
Sat 31 OctAlmere Centrum 20:27+2 min+4 min
Fri 30 Oct— 20:27No data—
Thu 29 Oct— 20:28+2 min+3 min
Wed 28 Oct— 20:23No data—
Tue 27 Oct— 20:24No data—
Mon 26 Oct— 20:26No data—
Sun 25 OctAlmere Centrum 20:28No data—
Sat 24 OctAlmere Centrum 20:260 min—
Fri 23 Oct— 20:28+4 min+5 min
Thu 22 Oct— 20:24No data—
Wed 21 Oct— 20:26No data—
Tue 20 Oct— 20:280 min—
Mon 19 Oct— 20:230 min—
Fri 16 Oct— 20:27No data—
Thu 15 Oct— 20:28No data—
Wed 14 Oct— 20:24No data—
Tue 13 Oct— 20:24No data—
Mon 12 Oct— 20:240 min—
Sun 11 OctAlmere Centrum 20:27+3 min+3 min
Sat 10 OctAlmere Centrum 20:30+7 min+7 min
Fri 9 Oct— 20:27+3 min+4 min
Thu 8 Oct— 20:530 min—
Wed 7 Oct— 20:350 min—
Tue 6 Oct— 20:23+2 min+2 min