Train NS 2679 Amsterdam Centraal → Almere Centrum

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

It does not run today

Last recorded run: Friday 20 November +2 min

Next service: Monday 21:38 from Amsterdam Centraal · Mon 23 Nov

Next departure 21:38 Monday · Amsterdam Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 13 full · 4 partial · 8 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 22 full · 6 partial · 18 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: +3 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

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

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

On-time by weekday

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

Stops and timetable

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

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