Train NS Int 9559 Antwerpen-Centraal – Amsterdam Zuid

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

It has not run yet today

Last recorded run: Monday 16 November +38 min

Next service: today 16:08 from Antwerpen-Centraal · Tue 17 Nov

Next departure 16:08 today · Antwerpen-Centraal
On-time · 30 days
65%
13/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
66%
19/29 runs under 3 min
RT coverage: 29 full · 0 partial · 55 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+24min
9 in 10 runs arrive with less than this
30 days: +29 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

  • Mon 16 Nov Max en route +38 min · last fix heading to Almere Buiten +38 min
  • Wed 4 Nov Max en route +30 min · last fix heading to Rotterdam Centraal +30 min
  • Fri 6 Nov Max en route +29 min · last fix heading to Almere Buiten +29 min
  • Sun 15 Nov Max en route +23 min · last fix heading to Amsterdam Zuid +23 min
  • Tue 6 Oct Max en route +13 min · last fix heading to Amsterdam Zuid +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 66% · 19
  • 3–10 min 14% · 4
  • 10–30 min 14% · 4
  • 30+ min 7% · 2

On-time by weekday

  • 83% M n=6
  • 50% T n=4
  • 50% W n=4
  • 100% T n=2
  • 33% F n=3
  • 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, 29 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
16:08on time on time
17:19 / 17:22≈ on time ≈ +11 min
17:48 / 17:50≈ +1 min ≈ +16 min
17:56+1 min +17 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
Mon 16 NovAlmere Buiten 19:52+38 min+38 min
Sun 15 NovAmsterdam Zuid 18:42+23 min+23 min
Sat 14 NovAlmere Buiten 18:390 min—
Fri 13 NovAlmere Buiten 18:42+5 min+5 min
Thu 12 NovAlmere Centrum 18:380 min—
Wed 11 NovAmsterdam Zuid 18:380 min+2 min
Tue 10 NovSchiphol Airport 18:09+10 min+10 min
Mon 9 NovAmsterdam Zuid 18:380 min—
Sun 8 NovRoosendaal 17:190 min—
Sat 7 NovRoosendaal 17:190 min—
Fri 6 NovAlmere Buiten 19:34+29 min+29 min
Thu 5 NovAmsterdam Zuid 18:39No data—
Wed 4 NovRotterdam Centraal 18:38+30 min+30 min
Tue 3 NovAmsterdam Zuid 19:14No data—
Mon 2 NovAmsterdam Zuid 18:39+1 min+2 min
Sun 1 NovAmsterdam Zuid 18:15+2 min+2 min
Sat 31 OctAlmere Buiten 18:41+1 min+1 min
Fri 30 OctAlmere Buiten 18:39No data—
Thu 29 OctAmsterdam Zuid 18:40No data—
Wed 28 OctAmsterdam Zuid 18:42+1 min—
Tue 27 OctAmsterdam Zuid 18:42No data—
Mon 26 OctAmsterdam Zuid 18:530 min—
Sun 25 OctAmsterdam Zuid 18:44No data—
Sat 24 OctAlmere Buiten 19:24+8 min+8 min
Fri 23 OctSchiphol Airport 18:05No data—
Thu 22 OctAlmere Centrum 19:36No data—
Wed 21 OctAlmere Buiten 19:38No data—
Tue 20 OctAlmere Buiten 18:440 min—
Mon 19 OctAlmere Buiten 18:440 min—
Sun 18 OctAmsterdam Zuid 18:21+7 min+7 min