Train NS Int 9544 Amsterdam Zuid – Antwerpen-Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November +23 min

Next service: today 14:03 from Amsterdam Zuid · Mon 16 Nov

Next departure 14:03 today · Amsterdam Zuid
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 26 full · 1 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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 +28 min · last fix heading to Rotterdam Centraal +23 min
  • Sun 11 Oct Max en route +19 min · last fix heading to Rotterdam Centraal +15 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Rotterdam Centraal +9 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 89% · 24
  • 3–10 min 4% · 1
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=5
  • 40% 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
14:03on time on time
14:09 / 14:11≈ on time ≈ on time
14:38 / 14:40≈ on time ≈ +1 min
15:52on time +2 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 NovRotterdam Centraal 15:54Partial coverage+23 min+28 min
Sat 14 NovRotterdam Centraal 15:530 min—
Fri 13 NovRotterdam Centraal 16:130 min—
Thu 12 NovRotterdam Centraal 16:130 min—
Wed 11 NovRotterdam Centraal 16:040 min—
Tue 10 NovRotterdam Centraal 16:120 min—
Mon 9 NovRotterdam Centraal 16:130 min—
Sun 8 NovBreda 16:09+2 min+2 min
Sat 7 NovBreda 15:070 min—
Fri 6 NovRotterdam Centraal 16:12No data—
Thu 5 NovRotterdam Centraal 16:13No data—
Wed 4 NovRotterdam Centraal 16:130 min—
Tue 3 NovRotterdam Centraal 16:52No data—
Mon 2 NovRotterdam Centraal 16:13No data—
Sun 1 NovRotterdam Centraal 16:050 min—
Sat 31 OctRotterdam Centraal 16:040 min—
Fri 30 OctRotterdam Centraal 14:56No data—
Thu 29 OctRotterdam Centraal 14:570 min—
Wed 28 OctRotterdam Centraal 16:120 min—
Tue 27 OctRotterdam Centraal 16:130 min—
Mon 26 OctRotterdam Centraal 16:12No data—
Sun 25 OctRotterdam Centraal 16:04No data—
Sat 24 OctRotterdam Centraal 16:040 min—
Fri 23 OctRotterdam Centraal 15:13No data—
Thu 22 OctRotterdam Centraal 16:12No data—
Wed 21 OctRotterdam Centraal 16:46No data—
Tue 20 OctRotterdam Centraal 14:570 min—
Mon 19 OctRotterdam Centraal 16:130 min—
Sun 18 OctRotterdam Centraal 16:00+9 min+9 min
Sat 17 OctRotterdam Centraal 15:47No data—