Train NS 2667 Amsterdam Centraal – Almere Centrum

Amsterdam Centraal 18:38 → Almere Centrum 18:58 Daily 0 h 20 min · 2 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:38 from Amsterdam Centraal · Thu 5 Nov

Next departure 18:38 today · Amsterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 8 full · 4 partial · 14 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 9 full · 4 partial · 32 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: +1 min

Last 30 days

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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
18:38on time on time
18:58+1 min +1 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
Wed 4 Nov— 19:04No data—
Mon 2 Nov— 18:59+1 min+1 min
Sun 1 NovAmsterdam Centraal 18:52No data—
Sat 31 OctAmsterdam Centraal 18:52No data—
Fri 30 OctAmsterdam Centraal 19:02No data—
Thu 29 Oct— 19:02+1 min+2 min
Wed 28 Oct— 19:06+1 min+1 min
Tue 27 Oct— 19:04No data—
Mon 26 Oct— 18:590 min—
Sun 25 OctAmsterdam Centraal 18:59No data—
Sat 24 OctAmsterdam Centraal 19:28No data—
Fri 23 OctAmsterdam Centraal 18:59Partial coverage0 min—
Thu 22 OctAmsterdam Centraal 19:02No data—
Wed 21 OctAmsterdam Centraal 19:02No data—
Tue 20 OctAmsterdam Centraal 19:04No data—
Mon 19 OctAmsterdam Centraal 18:590 min—
Fri 16 OctAmsterdam Centraal 18:57No data—
Thu 15 Oct— 19:04No data—
Wed 14 OctAmsterdam Centraal 19:04No data—
Tue 13 OctAmsterdam Centraal 19:00No data—
Mon 12 OctAmsterdam Centraal 19:00Partial coverage0 min—
Sun 11 OctAmsterdam Centraal 18:58Partial coverage0 min—
Sat 10 OctAmsterdam Centraal 18:58Partial coverage0 min—
Fri 9 Oct— 18:590 min—
Thu 8 Oct— 19:00+1 min—
Wed 7 Oct— 19:00+1 min+2 min
Tue 6 Oct— 19:02+2 min+3 min
Fri 2 OctAmsterdam Centraal 18:52No data—
Sun 27 SeptAmsterdam Centraal 18:53No data—
Sat 26 SeptAmsterdam Centraal 18:53No data—