Train NS 2667 Amsterdam Centraal → Almere Centrum

Amsterdam Centraal 18:38 → Almere Centrum 18:58 Mon, Tue, Wed, Thu, Fri, Sun 0 h 20 min · 2 stops NS (Nederlandse Spoorwegen)

NS 2667 Amsterdam Centraal–Almere Centrum: final delay under 3 min on 14 of its 17 runs with data in the last 30 days (82%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 06:27 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 18:38 from Amsterdam Centraal · Mon 23 Nov

Next departure 18:38 tomorrow · Amsterdam Centraal
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 10 full · 7 partial · 10 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 15 full · 11 partial · 31 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: +5 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

Worst days

  • Wed 18 Nov Max en route +8 min · last fix heading to Amsterdam Centraal +7 min
  • Mon 16 Nov Max en route +6 min · last fix heading to — +6 min
  • Thu 19 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=1
  • 75% W n=4
  • 80% T n=5
  • 100% F n=5
  • 100% 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, 26 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 +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 20 NovAmsterdam Centraal 19:00Partial coverage0 min—
Thu 19 Nov— 19:08+4 min+4 min
Wed 18 NovAmsterdam Centraal 19:14Partial coverage+7 min+8 min
Tue 17 Nov— 18:47No data—
Mon 16 Nov— 19:09+6 min+6 min
Sun 15 NovAmsterdam Centraal 19:04Partial coverageNo data—
Sat 14 NovAmsterdam Centraal 18:59Partial coverage0 min—
Fri 13 NovAmsterdam Centraal 18:59Partial coverage+1 min+1 min
Thu 12 Nov— 19:04+2 min+3 min
Wed 11 Nov— 19:02+1 min+1 min
Tue 10 Nov— 18:59No data—
Mon 9 Nov— 18:59+1 min+1 min
Sun 8 NovAmsterdam Centraal 18:59Partial coverage+1 min+1 min
Sat 7 NovAmsterdam Centraal 18:58Partial coverage+1 min+2 min
Fri 6 NovAmsterdam Centraal 18:59Partial coverage+2 min+2 min
Thu 5 Nov— 19:140 min—
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—