Train NS Int 9268 Rotterdam Centraal → Brussel-Zuid

Rotterdam Centraal 21:10 → Brussel-Zuid 23:39 Daily 2 h 29 min · 9 stops NS Int

NS Int 9268 Rotterdam Centraal–Brussel-Zuid: final delay under 3 min on 7 of its 7 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 17:07 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 21:10 from Rotterdam Centraal · Sun 22 Nov

Next departure 21:10 today · Rotterdam Centraal
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 1 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 10 full · 1 partial · 12 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 11 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:10on time on time
21:34 / 21:42≈ on time ≈ on time
22:00 / 22:01≈ on time ≈ on time
22:16 / 22:19≈ on time ≈ on time
22:23 / 22:25≈ on time ≈ on time
23:10 / 23:12≈ on time ≈ on time
23:23 / 23:31≈ on time ≈ on time
23:34 / 23:35≈ on time ≈ on time
23:39on 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
Sat 21 NovBreda 21:54Partial coverage0 min—
Sun 15 NovRoosendaal 21:590 min—
Sat 14 NovRoosendaal 21:540 min—
Sun 8 NovRoosendaal 21:540 min—
Sat 7 NovRoosendaal 21:540 min—
Sun 1 NovBreda 21:540 min—
Sat 31 OctBreda 21:56No data—
Sat 24 OctBreda 21:570 min—
Sun 18 OctBreda 21:580 min—
Sat 17 OctBreda 21:560 min—
Sun 11 OctBreda 21:560 min—
Sat 10 OctBreda 21:56+2 min+2 min
Sat 3 OctRoosendaal 21:55No data—
Sun 27 SeptBreda 21:56No data—
Sat 26 SeptBreda 21:56No data—
Sun 20 SeptBreda 21:57No data—
Sat 19 SeptBreda 21:56No data—
Sun 13 SeptBreda 21:59No data—
Sat 12 SeptBreda 21:57No data—
Sun 6 SeptBreda 21:57No data—
Sat 5 SeptBreda 21:56No data—
Sun 30 AugBreda 21:57No data—
Sat 29 AugBreda 21:56No data—