Train NS Int 9551 Brussel-Zuid – Amsterdam Zuid

Brussel-Zuid 13:57 → Amsterdam Zuid 15:56 Daily 1 h 59 min · 5 stops NS Int

Running now · updated 14:16

Heading to Amsterdam Zuid No data

Estimated arrival at Amsterdam Zuid 15:56 · 145 km/h

  1. Brussel-Zuid13:57
  2. Antwerpen-Centraal14:31
  3. Rotterdam Centraal15:17
  4. Schiphol Airport15:48
  5. Amsterdam Zuid15:56
On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 14 full · 1 partial · 15 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 17 full · 1 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+14min
9 in 10 runs arrive with less than this
30 days: +17 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 4 Nov Max en route +38 min · last fix heading to Almere Centrum +38 min
  • Sat 24 Oct Max en route +21 min · last fix heading to Almere Buiten +21 min
  • Thu 8 Oct Max en route +12 min · last fix heading to Almere Buiten +11 min
  • Sun 18 Oct Max en route +11 min · last fix heading to Amsterdam Zuid +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 0% · 0
  • 10–30 min 17% · 3
  • 30+ min 6% · 1

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 67% W n=3
  • 50% T n=2
  • 100% F n=1
  • 67% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 18 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 10Today
13:57on time on time
14:31 / 14:36≈ on time ≈ +5 min
15:17 / 15:22≈ on time ≈ +11 min
15:48 / 15:50≈ on time ≈ +15 min
15:56on time +16 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
Fri 6 NovRotterdam Centraal 14:14No data—
Thu 5 NovAlmere Buiten 16:39No data—
Wed 4 NovAlmere Centrum 17:39+38 min+38 min
Tue 3 NovAlmere Buiten 17:19No data—
Mon 2 NovAlmere Buiten 17:08No data—
Sun 1 NovAmsterdam Zuid 16:17+2 min+2 min
Sat 31 OctAlmere Buiten 16:390 min—
Fri 30 OctAlmere Buiten 16:40No data—
Thu 29 OctAlmere Buiten 16:410 min—
Wed 28 OctAlmere Buiten 16:410 min—
Tue 27 OctAlmere Buiten 16:400 min—
Mon 26 OctAlmere Buiten 16:41No data—
Sun 25 OctAmsterdam Zuid 16:14No data—
Sat 24 OctAlmere Buiten 17:18+21 min+21 min
Fri 23 OctAlmere Buiten 16:39No data—
Thu 22 OctAlmere Buiten 16:45No data—
Wed 21 OctAmsterdam Zuid 17:09No data—
Tue 20 OctSchiphol Airport 16:120 min—
Mon 19 OctAlmere Buiten 16:400 min—
Sun 18 OctAmsterdam Zuid 16:25+11 min+11 min
Sat 17 OctAmsterdam Zuid 16:15No data—
Fri 16 OctAlmere Buiten 16:41No data—
Thu 15 OctRotterdam Centraal 15:35No data—
Wed 14 OctAlmere Buiten 16:41No data—
Tue 13 OctRotterdam Centraal 16:390 min—
Mon 12 Oct— 15:19No data—
Sun 11 OctSchiphol Airport 16:18Partial coverage+2 min+3 min
Sat 10 OctRotterdam Centraal 15:360 min—
Fri 9 OctRotterdam Centraal 15:490 min—
Thu 8 OctAlmere Buiten 17:00+11 min+12 min