Train NS 2469 Rotterdam Centraal – Almere Centrum

Rotterdam Centraal 19:52 → Almere Centrum 20:47 Daily 0 h 55 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: tomorrow 19:52 from Rotterdam Centraal · Mon 9 Nov

Next departure 19:52 tomorrow · Rotterdam Centraal
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 16 full · 1 partial · 9 no data
On-time · 90 days
82%
28/34 runs under 3 min
RT coverage: 33 full · 1 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 6 Oct Max en route +19 min · last fix heading to — +19 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Rotterdam Centraal +6 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Rotterdam Centraal +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 15% · 5
  • On time 68% · 23
  • 3–10 min 15% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 0% T n=1
  • 67% W n=3
  • 67% T n=3
  • 67% F n=6
  • 100% S n=9
  • 86% S n=7

Stops and timetable

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

Last 90 days, 34 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
19:52on time on time
20:18 / 20:19≈ on time ≈ +2 min
20:25 / 20:26≈ on time ≈ +2 min
20:30 / 20:31≈ on time ≈ +3 min
20:47on time +4 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— 20:49+1 min+3 min
Thu 5 Nov— 20:49No data—
Wed 4 Nov— 20:54+4 min+4 min
Mon 2 Nov— 20:480 min—
Sun 1 NovDuivendrecht 20:490 min—
Sat 31 OctDuivendrecht 20:470 min—
Fri 30 Oct— 20:480 min—
Thu 29 Oct— 20:51+2 min+2 min
Wed 28 Oct— 21:080 min—
Tue 27 Oct— 21:09No data—
Mon 26 Oct— 21:07No data—
Sun 25 OctDuivendrecht 20:48No data—
Sat 24 OctDuivendrecht 21:060 min—
Fri 23 Oct— 20:52+2 min+4 min
Thu 22 Oct— 20:490 min—
Wed 21 Oct— 20:50No data—
Mon 19 Oct— 21:33No data—
Sun 18 OctRotterdam Centraal 20:41+6 min+8 min
Sat 17 OctSchiphol Airport 20:370 min—
Fri 16 OctRotterdam Centraal 20:56Partial coverage+4 min+4 min
Thu 15 Oct— 20:50No data—
Wed 14 Oct— 21:08No data—
Tue 13 Oct— 20:49No data—
Mon 12 Oct— 20:480 min—
Sun 11 OctDuivendrecht 20:49+1 min+2 min
Sat 10 OctDuivendrecht 20:53+2 min+2 min
Fri 9 Oct— 20:55+3 min+3 min
Thu 8 Oct— 20:55+4 min+4 min
Wed 7 Oct— 20:51+2 min+3 min
Tue 6 Oct— 21:08+19 min+19 min