Train NS 2630 Almere Centrum → Amsterdam Centraal

Almere Centrum 10:31 → Amsterdam Centraal 10:52 Mon, Tue, Wed, Thu, Fri, Sun 0 h 21 min · 2 stops NS (Nederlandse Spoorwegen)

NS 2630 Almere Centrum–Amsterdam Centraal: final delay under 3 min on 17 of its 19 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 17:49 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 10:31 from Almere Centrum · Mon 23 Nov

Next departure 10:31 tomorrow · Almere Centrum
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 17 full · 2 partial · 8 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 25 full · 3 partial · 46 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 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 7 Nov Max en route +10 min · last fix heading to Almere Centrum +10 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Almere Centrum +4 min
  • Sat 14 Nov Max en route +3 min · last fix heading to Almere Centrum +3 min

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 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
10:31on time on time
10:52on time +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 NovAlmere Centrum 10:53Partial coverage0 min—
Thu 19 NovAlmere Centrum 10:530 min—
Wed 18 NovAlmere Centrum 10:540 min—
Tue 17 NovAlmere Centrum 10:530 min—
Mon 16 NovAlmere Centrum 10:540 min—
Sun 15 NovAlmere Centrum 10:54+1 min+1 min
Sat 14 NovAlmere Centrum 10:59+3 min+3 min
Fri 13 NovAlmere Centrum 10:53Partial coverage0 min—
Thu 12 NovAlmere Centrum 10:540 min—
Wed 11 NovAlmere Centrum 10:58+3 min+4 min
Mon 9 NovAlmere Centrum 10:530 min—
Sun 8 NovAlmere Centrum 10:530 min—
Sat 7 NovAlmere Centrum 11:04+10 min+10 min
Fri 6 NovAlmere Centrum 10:53No data—
Thu 5 NovAlmere Centrum 10:58No data—
Wed 4 NovAlmere Centrum 10:54+1 min—
Tue 3 NovAlmere Centrum 10:53No data—
Mon 2 NovAlmere Centrum 10:58No data—
Sun 1 NovAlmere Centrum 10:58+2 min+2 min
Sat 31 OctAlmere Centrum 10:450 min—
Fri 30 OctAlmere Centrum 10:58No data—
Thu 29 OctAlmere Centrum 10:570 min—
Wed 28 OctAlmere Centrum 10:540 min—
Tue 27 OctAlmere Centrum 10:56No data—
Mon 26 OctAlmere Centrum 10:53No data—
Sun 25 OctAlmere Centrum 10:53No data—
Sat 24 OctAlmere Centrum 10:56+2 min+3 min
Fri 23 OctAlmere Centrum 10:53No data—
Thu 22 OctAlmere Centrum 10:530 min—
Wed 21 OctAlmere Centrum 10:56No data—