Train NS Int 9528 Amsterdam Zuid – Antwerpen-Centraal

Amsterdam Zuid 10:03 → Antwerpen-Centraal 11:52 Daily 1 h 49 min · 4 stops NS Int

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 12:09 +16 min

  1. Amsterdam Zuid10:03
  2. Schiphol Airport10:09
  3. Rotterdam Centraal10:38
  4. Antwerpen-Centraal11:52

Next service: tomorrow 10:03 from Amsterdam Zuid · Mon 16 Nov

Next departure 10:03 tomorrow · Amsterdam Zuid
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 19 full · 2 partial · 9 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 26 full · 2 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +11 min

Last 30 days

Arrival delay at Antwerpen-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

  • Sun 15 Nov Max en route +16 min · last fix heading to Rotterdam Centraal +16 min
  • Sun 18 Oct Max en route +16 min · last fix heading to Rotterdam Centraal +15 min
  • Sat 14 Nov Max en route +14 min · last fix heading to Rotterdam Centraal +11 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 89% · 25
  • 3–10 min 0% · 0
  • 10–30 min 11% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=6
  • 100% W n=4
  • 100% T n=2
  • 100% F n=2
  • 83% S n=6
  • 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:03on time on time
10:09 / 10:11≈ on time ≈ on time
10:38 / 10:40≈ on time ≈ on time
11:52on time on time

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 NovRotterdam Centraal 12:09Partial coverage+16 min+16 min
Sat 14 NovRotterdam Centraal 12:04Partial coverage+11 min+14 min
Fri 13 NovRotterdam Centraal 12:120 min—
Thu 12 NovRotterdam Centraal 12:130 min—
Wed 11 NovRotterdam Centraal 11:340 min—
Tue 10 NovRotterdam Centraal 12:120 min—
Mon 9 NovRotterdam Centraal 12:120 min+24 min
Sun 8 NovRoosendaal 12:040 min—
Sat 7 NovBreda 11:080 min+4 min
Fri 6 NovRotterdam Centraal 11:09No data—
Thu 5 NovRotterdam Centraal 12:12No data—
Wed 4 NovRotterdam Centraal 12:130 min—
Tue 3 NovRotterdam Centraal 10:540 min—
Mon 2 NovRotterdam Centraal 12:140 min—
Sun 1 NovAmsterdam Zuid 11:010 min—
Sat 31 OctRotterdam Centraal 10:580 min—
Fri 30 OctRotterdam Centraal 12:12No data—
Thu 29 OctRotterdam Centraal 10:56No data—
Wed 28 OctRotterdam Centraal 12:120 min—
Tue 27 OctRotterdam Centraal 12:130 min—
Mon 26 OctRotterdam Centraal 12:12No data—
Sun 25 OctRotterdam Centraal 12:04No data—
Sat 24 OctRotterdam Centraal 12:040 min—
Fri 23 OctRotterdam Centraal 12:22No data—
Thu 22 OctRotterdam Centraal 12:12No data—
Wed 21 OctRotterdam Centraal 12:12No data—
Tue 20 OctRotterdam Centraal 12:120 min—
Mon 19 OctRotterdam Centraal 12:120 min—
Sun 18 OctRotterdam Centraal 11:14+15 min+16 min
Sat 17 OctRotterdam Centraal 11:420 min—