Train NS Int 9531 Antwerpen-Centraal → Amsterdam Centraal

Antwerpen-Centraal 09:42 → Amsterdam Centraal 11:15 Daily 1 h 33 min · 3 stops NS Int

Running now · updated 10:33

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 11:15 · 89 km/h

  1. Antwerpen-Centraal09:42
  2. Rotterdam Centraal10:20
  3. Amsterdam Centraal11:15

Today it is running no worse than usual: typical arrival delay is 0 min; 81% of the last 21 runs arrived on time.

On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 20 full · 1 partial · 9 no data
On-time · 90 days
81%
26/32 runs under 3 min
RT coverage: 31 full · 1 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+18min
9 in 10 runs arrive with less than this
30 days: +19 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

  • Mon 9 Nov Max en route +48 min · last fix heading to Almere Centrum +46 min
  • Wed 7 Oct Max en route +39 min · last fix heading to Almere Buiten +38 min
  • Mon 16 Nov Max en route +30 min · last fix heading to Almere Buiten +30 min
  • Thu 19 Nov Max en route +19 min · last fix heading to Almere Buiten +19 min
  • Sat 24 Oct Max en route +15 min · last fix heading to Almere Buiten +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 26
  • 3–10 min 3% · 1
  • 10–30 min 6% · 2
  • 30+ min 9% · 3

On-time by weekday

  • 33% M n=3
  • 100% T n=6
  • 80% W n=5
  • 67% T n=3
  • 100% F n=3
  • 71% S n=7
  • 100% S n=5

Stops and timetable

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

Last 90 days, 32 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 10Today
09:42on time on time
10:20 / 10:22≈ on time ≈ +8 min
11:15on time +19 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
Sat 21 NovRotterdam Centraal 10:29Partial coverage0 min—
Fri 20 NovAlmere Buiten 11:390 min—
Thu 19 NovAlmere Buiten 12:14+19 min+19 min
Wed 18 NovAlmere Buiten 11:390 min—
Tue 17 NovAlmere Buiten 11:39+2 min+2 min
Mon 16 NovAlmere Buiten 12:20+30 min+30 min
Sun 15 NovAmsterdam Zuid 11:140 min—
Sat 14 NovAlmere Buiten 11:390 min+1 min
Fri 13 NovAlmere Buiten 11:39+2 min+2 min
Thu 12 NovAlmere Buiten 11:39+1 min+2 min
Wed 11 NovAlmere Buiten 11:390 min—
Tue 10 NovSchiphol Airport 11:030 min—
Mon 9 NovAlmere Centrum 12:38+46 min+48 min
Sun 8 NovRoosendaal 10:190 min—
Sat 7 NovRoosendaal 10:190 min—
Fri 6 NovAlmere Buiten 12:19No data—
Thu 5 NovAlmere Buiten 11:39No data—
Wed 4 NovSchiphol Airport 11:04+3 min+3 min
Tue 3 NovAlmere Buiten 11:40No data—
Mon 2 NovAlmere Buiten 11:39No data—
Sun 1 NovAmsterdam Zuid 11:150 min—
Sat 31 OctSchiphol Airport 11:06+2 min+3 min
Fri 30 OctAlmere Buiten 11:46No data—
Thu 29 OctAlmere Buiten 11:39No data—
Wed 28 OctAlmere Buiten 11:390 min—
Tue 27 OctAlmere Buiten 11:420 min—
Mon 26 OctAlmere Buiten 11:39No data—
Sun 25 OctAmsterdam Zuid 11:14No data—
Sat 24 OctAlmere Buiten 12:07+15 min+15 min
Fri 23 OctAlmere Buiten 12:18No data—