Train NS Int 9516 Amsterdam Zuid – Brussel-Zuid

Amsterdam Zuid 07:04 → Brussel-Zuid 09:11 Daily 2 h 07 min · 5 stops NS Int

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 07:04 from Amsterdam Zuid · Sat 7 Nov

Next departure 07:04 today · Amsterdam Zuid
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 11 full · 14 partial · 4 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 14 full · 14 partial · 60 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

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

  • Early 0% · 0
  • On time 100% · 28
  • 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=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
07:04on time on time
07:10 / 07:12≈ on time ≈ on time
07:39 / 07:42≈ on time ≈ on time
08:26 / 08:37≈ on time ≈ on time
09:11on 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
Fri 6 NovRotterdam Centraal 09:12No data—
Thu 5 NovRotterdam Centraal 07:54No data—
Wed 4 NovRotterdam Centraal 09:13Partial coverage0 min—
Tue 3 NovRotterdam Centraal 09:12Partial coverage0 min—
Mon 2 NovRotterdam Centraal 09:13No data—
Sun 1 NovRotterdam Centraal 09:040 min—
Sat 31 OctRotterdam Centraal 07:560 min—
Fri 30 OctRotterdam Centraal 09:120 min—
Thu 29 OctRotterdam Centraal 07:56Partial coverage0 min—
Wed 28 OctRotterdam Centraal 09:12Partial coverage0 min—
Tue 27 OctRotterdam Centraal 09:13Partial coverage0 min—
Mon 26 OctRotterdam Centraal 09:12Partial coverage0 min—
Sun 25 OctRotterdam Centraal 09:04No data—
Sat 24 OctRotterdam Centraal 09:040 min—
Fri 23 OctRotterdam Centraal 09:120 min—
Thu 22 OctRotterdam Centraal 09:12Partial coverage0 min—
Wed 21 OctRotterdam Centraal 09:12Partial coverage0 min—
Tue 20 OctRotterdam Centraal 07:56Partial coverage0 min—
Mon 19 OctRotterdam Centraal 09:12Partial coverage0 min—
Sun 18 OctRotterdam Centraal 08:420 min—
Sat 17 OctRotterdam Centraal 08:420 min—
Fri 16 OctRotterdam Centraal 09:120 min—
Thu 15 OctRotterdam Centraal 09:13Partial coverage0 min+5 min
Wed 14 OctRotterdam Centraal 09:12Partial coverage0 min—
Tue 13 OctRotterdam Centraal 09:12Partial coverage0 min—
Mon 12 OctRotterdam Centraal 09:12Partial coverage0 min—
Sun 11 OctRotterdam Centraal 09:040 min—
Sat 10 OctRotterdam Centraal 09:040 min—
Fri 9 OctRotterdam Centraal 09:120 min—
Thu 8 OctRotterdam Centraal 09:130 min—