Train NS 2470 Almere Centrum – Rotterdam Centraal

Almere Centrum 20:11 → Rotterdam Centraal 21:08 Daily 0 h 57 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 21:09 0 min

  1. Almere Centrum20:11
  2. Duivendrecht20:28
  3. Amsterdam Zuid20:32
  4. Schiphol Airport20:40
  5. Rotterdam Centraal21:08

Next service: tomorrow 20:11 from Almere Centrum · Sat 21 Nov

Next departure 20:11 tomorrow · Almere Centrum
On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 23 full · 0 partial · 3 no data
On-time · 90 days
84%
37/44 runs under 3 min
RT coverage: 44 full · 0 partial · 10 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 Rotterdam 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

  • Thu 29 Oct Max en route +15 min · last fix heading to — +14 min
  • Mon 5 Oct Max en route +11 min · last fix heading to — +11 min
  • Fri 16 Oct Max en route +8 min · last fix heading to — +8 min
  • Sun 18 Oct Max en route +8 min · last fix heading to Schiphol Airport +7 min
  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 82% · 36
  • 3–10 min 11% · 5
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=3
  • 60% W n=5
  • 86% T n=7
  • 71% F n=7
  • 100% S n=8
  • 86% S n=7

Stops and timetable

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

Last 90 days, 44 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
20:11on time on time
20:28≈ on time ≈ +2 min
20:32 / 20:34≈ on time ≈ +2 min
20:40 / 20:41≈ on time ≈ +3 min
21:08on 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 20 Nov— 21:090 min—
Thu 19 Nov— 21:090 min+2 min
Wed 18 Nov— 21:14+4 min+4 min
Tue 17 Nov— 21:090 min—
Mon 16 Nov— 21:09+1 min—
Sun 15 NovSchiphol Airport 21:12+2 min+4 min
Sat 14 NovSchiphol Airport 21:09+1 min+2 min
Fri 13 Nov— 21:12+2 min+3 min
Thu 12 Nov— 21:090 min—
Wed 11 Nov— 21:090 min+1 min
Tue 10 Nov— 21:090 min+1 min
Mon 9 Nov— 21:090 min—
Fri 6 Nov— 21:13+3 min+3 min
Thu 5 Nov— 21:090 min—
Wed 4 Nov— 21:18+5 min+5 min
Sun 1 NovSchiphol Airport 21:090 min—
Sat 31 OctSchiphol Airport 21:110 min—
Fri 30 Oct— 21:160 min—
Thu 29 Oct— 21:37+14 min+15 min
Wed 28 Oct— 21:090 min—
Tue 27 Oct— 21:10No data—
Mon 26 Oct— 21:09No data—
Sun 25 OctSchiphol Airport 21:09No data—
Sat 24 OctSchiphol Airport 21:240 min—
Fri 23 Oct— 21:090 min—
Thu 22 Oct— 21:100 min—
Wed 21 Oct— 21:14No data—
Tue 20 Oct— 21:09No data—
Mon 19 Oct— 21:090 min—
Sun 18 OctSchiphol Airport 21:19+7 min+8 min