Train NS Int 9572 Amsterdam Zuid – Brussel-Zuid

Amsterdam Zuid 21:03 → Brussel-Zuid 23:48 Daily 2 h 45 min · 5 stops NS Int

It has not run yet today

Last recorded run: Sunday 15 November 0 min

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

Next departure 21:03 today · Amsterdam Zuid
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 15 full · 2 partial · 8 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 23 full · 2 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Brussel-Zuid, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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:03on time on time
21:09 / 21:11≈ on time ≈ on time
21:38 / 21:40≈ on time ≈ on time
22:48 / 22:53≈ on time ≈ on time
23:48on 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 23:49Partial coverage0 min—
Sat 14 NovRotterdam Centraal 21:54Partial coverage0 min—
Fri 13 Nov— 23:120 min—
Thu 12 Nov— 23:120 min—
Wed 11 Nov— 23:050 min—
Tue 10 Nov— 23:120 min—
Mon 9 Nov— 23:120 min—
Sun 8 NovBreda 22:190 min—
Sat 7 NovBreda 23:070 min—
Fri 6 Nov— 23:120 min—
Thu 5 Nov— 23:13No data—
Wed 4 Nov— 22:080 min—
Sun 1 NovRotterdam Centraal 23:040 min+1 min
Sat 31 OctRotterdam Centraal 23:04No data—
Fri 30 Oct— 23:12No data—
Wed 28 Oct— 23:12No data—
Tue 27 Oct— 23:120 min—
Mon 26 Oct— 23:12No data—
Sun 25 OctRotterdam Centraal 23:04No data—
Sat 24 OctRotterdam Centraal 23:04No data—
Fri 23 Oct— 23:120 min—
Wed 21 Oct— 23:12No data—
Tue 20 Oct— 23:120 min—
Mon 19 Oct— 23:120 min—
Sun 18 OctRotterdam Centraal 23:040 min—
Sat 17 OctRotterdam Centraal 23:04No data—
Fri 16 Oct— 23:120 min—
Thu 15 Oct— 23:14No data—
Wed 14 Oct— 23:120 min—
Sun 11 OctRotterdam Centraal 23:040 min—