Train NS Int 9255 Brussel-Zuid – Rotterdam Centraal

Brussel-Zuid 16:44 → Rotterdam Centraal 18:50 Daily 2 h 06 min · 10 stops NS Int

It has not run yet today

Last recorded run: Sunday 1 November +5 min

Next service: tomorrow 16:44 from Brussel-Zuid · Sat 7 Nov

Next departure 16:44 tomorrow · Brussel-Zuid
On-time · 30 days
75%
9/12 runs under 3 min
RT coverage: 9 full · 3 partial · 7 no data
On-time · 90 days
75%
9/12 runs under 3 min
RT coverage: 9 full · 3 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

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

  • Fri 9 Oct Max en route +8 min · last fix heading to Breda +8 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Breda +6 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Breda +5 min

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 100% W n=1
  • — T n=0
  • 75% F n=4
  • 100% S n=3
  • 33% S n=3

Stops and timetable

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

Last 90 days, 12 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
16:44on time on time
16:48 / 16:49≈ on time ≈ on time
16:53 / 16:56≈ on time ≈ on time
17:07 / 17:11≈ on time ≈ +1 min
17:22 / 17:24≈ on time ≈ +2 min
17:36 / 17:38≈ on time ≈ +3 min
17:42 / 17:45≈ on time ≈ +3 min
17:59 / 18:01≈ on time ≈ +4 min
18:19 / 18:26≈ on time ≈ +5 min
18:50on time +6 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 1 NovBreda 18:44Partial coverage+5 min+5 min
Sat 31 OctBreda 18:41Partial coverage0 min—
Fri 30 OctBreda 18:40Partial coverage0 min—
Sun 25 OctBreda 18:45No data—
Sat 24 OctBreda 18:430 min—
Fri 23 OctBreda 18:400 min—
Thu 22 OctBreda 18:40No data—
Wed 21 OctBreda 18:40No data—
Tue 20 OctBreda 18:40No data—
Mon 19 OctBreda 18:40No data—
Sun 18 OctBreda 18:46+6 min+7 min
Sat 17 OctBreda 18:440 min—
Fri 16 OctBreda 18:440 min—
Thu 15 OctBreda 18:40No data—
Wed 14 OctBreda 18:400 min—
Tue 13 OctBreda 18:400 min—
Sun 11 OctBreda 18:400 min—
Sat 10 OctBreda 18:40No data—
Fri 9 OctBreda 18:40+8 min+8 min
Sun 4 OctRoosendaal 18:36No data—
Sat 3 OctRoosendaal 18:37No data—
Fri 2 OctBreda 18:40No data—
Sun 27 SeptBreda 18:42No data—
Sat 26 SeptBreda 18:41No data—
Fri 25 SeptBreda 18:40No data—
Sun 20 SeptBreda 18:41No data—
Sat 19 SeptBreda 18:40No data—
Fri 18 SeptBreda 18:40No data—
Sun 13 SeptBreda 18:40No data—
Sat 12 SeptBreda 18:40No data—