Train NS 2683 Amsterdam Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 22:38 from Amsterdam Centraal · Sat 7 Nov

Next departure 22:38 today · Amsterdam Centraal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 11 full · 1 partial · 13 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 23 Oct Max en route +12 min · last fix heading to — +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 75% F n=4
  • 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, 15 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
22:38on time +1 min
22: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 6 Nov— 22:580 min—
Thu 5 Nov— 22:58No data—
Wed 4 Nov— 22:580 min—
Mon 2 Nov— 22:59+1 min+2 min
Sun 1 NovAmsterdam Centraal 22:52No data—
Sat 31 OctAmsterdam Centraal 22:59No data—
Thu 29 Oct— 23:03+2 min+3 min
Wed 28 Oct— 22:58No data—
Tue 27 Oct— 22:590 min—
Mon 26 Oct— 22:59No data—
Sun 25 OctAmsterdam Centraal 22:59No data—
Sat 24 OctAmsterdam Centraal 23:25No data—
Fri 23 Oct— 23:22+12 min+12 min
Thu 22 Oct— 23:00No data—
Wed 21 Oct— 22:580 min—
Tue 20 Oct— 22:58No data—
Mon 19 Oct— 23:00No data—
Fri 16 Oct— 22:590 min—
Thu 15 Oct— 22:58No data—
Wed 14 Oct— 22:58No data—
Tue 13 Oct— 23:05No data—
Mon 12 Oct— 22:580 min—
Sun 11 OctAmsterdam Centraal 22:58Partial coverage+1 min+2 min
Sat 10 Oct— 22:59+1 min+1 min
Fri 9 Oct— 22:580 min—
Thu 8 Oct— 22:580 min—
Wed 7 Oct— 22:580 min—
Tue 6 Oct— 22:58+1 min+1 min
Sun 27 SeptAmsterdam Centraal 22:53No data—
Sat 26 SeptAmsterdam Centraal 22:52No data—