Train NS Int 9535 Antwerpen-Centraal – Amsterdam Zuid

Antwerpen-Centraal 10:08 → Amsterdam Zuid 11:56 Daily 1 h 48 min · 4 stops NS Int

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 10:08 from Antwerpen-Centraal · Mon 16 Nov

Next departure 10:08 today · Antwerpen-Centraal
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
79%
22/28 runs under 3 min
RT coverage: 28 full · 0 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Amsterdam Zuid, 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 10 Nov Max en route +49 min · last fix heading to Schiphol Airport +49 min
  • Mon 9 Nov Max en route +19 min · last fix heading to Almere Buiten +19 min
  • Thu 8 Oct Max en route +13 min · last fix heading to Almere Buiten +12 min
  • Sat 14 Nov Max en route +10 min · last fix heading to Almere Buiten +9 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Rotterdam Centraal +5 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 79% · 22
  • 3–10 min 11% · 3
  • 10–30 min 7% · 2
  • 30+ min 4% · 1

On-time by weekday

  • 75% M n=4
  • 80% T n=5
  • 100% W n=4
  • 67% T n=3
  • 100% F n=2
  • 80% S n=5
  • 60% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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:08on time on time
11:19 / 11:22≈ on time ≈ +7 min
11:48 / 11:50≈ on time ≈ +9 min
11:56on time +10 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
Sun 15 NovAmsterdam Zuid 12:130 min—
Sat 14 NovAlmere Buiten 12:54+9 min+10 min
Fri 13 NovAlmere Buiten 12:39+1 min+1 min
Thu 12 NovAlmere Buiten 12:390 min—
Wed 11 NovAlmere Buiten 12:390 min+2 min
Tue 10 NovSchiphol Airport 12:48+49 min+49 min
Mon 9 NovAlmere Buiten 13:13+19 min+19 min
Sun 8 NovRoosendaal 11:190 min—
Sat 7 NovRoosendaal 11:190 min—
Fri 6 NovAlmere Buiten 12:39No data—
Thu 5 NovAlmere Buiten 12:39No data—
Wed 4 NovAlmere Buiten 12:39+1 min+1 min
Tue 3 NovAlmere Buiten 13:040 min—
Mon 2 NovAlmere Buiten 12:390 min—
Sun 1 NovAmsterdam Zuid 12:150 min—
Sat 31 OctAlmere Buiten 12:40+1 min+2 min
Fri 30 OctAlmere Buiten 12:39No data—
Thu 29 OctAlmere Buiten 12:400 min—
Wed 28 OctAlmere Buiten 13:200 min—
Tue 27 OctAlmere Buiten 12:56No data—
Mon 26 OctAlmere Buiten 13:00No data—
Sun 25 OctSchiphol Airport 13:08No data—
Sat 24 OctAlmere Buiten 12:400 min+2 min
Fri 23 OctAlmere Buiten 13:00No data—
Thu 22 OctAlmere Buiten 13:20No data—
Wed 21 Oct— 11:29No data—
Tue 20 OctAlmere Buiten 12:400 min—
Mon 19 OctAlmere Buiten 12:570 min—
Sun 18 OctRotterdam Centraal 12:30+5 min+5 min
Sat 17 OctAmsterdam Zuid 12:15No data—