Train NS Int 9272 Roosendaal – Brussel-Zuid

Roosendaal 22:40 → Brussel-Zuid 00:17 Daily 1 h 37 min · 8 stops NS Int

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 22:40 from Roosendaal · Fri 13 Nov

Next departure 22:40 today · Roosendaal
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 3 full · 2 partial · 3 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 4 full · 2 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Sun 18 Oct Max en route +5 min · last fix heading to Breda +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 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=2
  • 75% S n=4

Stops and timetable

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

Last 90 days, 6 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
22:40on time on time
23:16 / 23:19— —
23:23 / 23:25— —
23:37 / 23:39— —
23:50 / 23:53— —
00:05 / 00:08— —
00:12 / 00:13— —
00:17— —

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 8 NovRoosendaal 22:54Partial coverage0 min—
Sat 7 NovRoosendaal 22:54Partial coverage0 min—
Sun 1 NovBreda 22:540 min—
Sat 31 OctBreda 22:56No data—
Sun 25 OctBreda 22:59No data—
Sat 24 OctRotterdam Centraal 22:430 min—
Sun 18 OctBreda 23:05+5 min+5 min
Sat 17 OctBreda 23:08No data—
Sun 11 OctBreda 23:000 min—
Sun 4 OctRoosendaal 23:01No data—
Sat 3 OctRoosendaal 22:51No data—
Sun 27 SeptBreda 23:04No data—
Sat 26 SeptBreda 22:56No data—
Sun 20 SeptBreda 23:14No data—
Sat 19 SeptBreda 22:56No data—
Sun 13 SeptBreda 22:57No data—
Sat 12 SeptBreda 22:56No data—
Sun 6 SeptBreda 22:56No data—
Sat 5 SeptBreda 22:56No data—
Sun 30 AugBreda 22:56No data—
Sat 29 AugBreda 22:56No data—
Sun 23 AugBreda 23:13No data—
Sat 22 AugBreda 22:56No data—
Sun 16 AugBreda 22:59No data—