Train NS Int 9579 Antwerpen-Centraal – Amsterdam Zuid

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

It has not run yet today

Last recorded run: Sunday 15 November +12 min

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

Next departure 21:08 today · Antwerpen-Centraal
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 17 full · 0 partial · 10 no data
On-time · 90 days
81%
22/27 runs under 3 min
RT coverage: 27 full · 0 partial · 26 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

  • Wed 14 Oct Max en route +44 min · last fix heading to — +44 min
  • Fri 6 Nov Max en route +18 min · last fix heading to — +18 min
  • Sun 15 Nov Max en route +12 min · last fix heading to Amsterdam Zuid +12 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Amsterdam Zuid +9 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Roosendaal +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 22
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 4% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
21:08on time on time
22:19 / 22:22≈ on time ≈ +5 min
22:48 / 22:50≈ on time ≈ +7 min
22:56on time +7 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 23:24+12 min+12 min
Sat 14 NovAmsterdam Zuid 23:140 min—
Fri 13 Nov— 00:040 min+34 min
Thu 12 Nov— 22:580 min—
Wed 11 Nov— 22:59+3 min+4 min
Tue 10 Nov— 22:570 min—
Mon 9 Nov— 22:580 min—
Sun 8 NovRoosendaal 22:190 min—
Sat 7 NovRoosendaal 22:24+5 min+5 min
Fri 6 Nov— 23:32+18 min+18 min
Thu 5 Nov— 22:57No data—
Wed 4 Nov— 22:570 min—
Mon 2 Nov— 22:580 min—
Sun 1 NovAmsterdam Zuid 23:140 min—
Sat 31 OctAmsterdam Zuid 00:01No data—
Fri 30 Oct— 22:57No data—
Wed 28 Oct— 23:04No data—
Tue 27 Oct— 22:570 min—
Mon 26 Oct— 22:59No data—
Sun 25 OctAmsterdam Zuid 23:14No data—
Sat 24 OctRotterdam Centraal 23:02No data—
Fri 23 Oct— 22:57No data—
Thu 22 Oct— 23:00No data—
Wed 21 Oct— 22:57No data—
Tue 20 Oct— 23:000 min—
Mon 19 Oct— 23:020 min—
Sun 18 OctAmsterdam Zuid 23:51+9 min+9 min
Sat 17 OctAmsterdam Zuid 23:14No data—
Fri 16 Oct— 22:570 min—
Thu 15 Oct— 22:59No data—