Train NS Int 9243 Brussel-Zuid – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Tuesday 3 November No data

Next service: today 13:44 from Brussel-Zuid · Thu 5 Nov

Next departure 13:44 today · Brussel-Zuid
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 12 full · 8 partial · 6 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 14 full · 8 partial · 62 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: +9 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

  • Sun 11 Oct Max en route +24 min · last fix heading to Breda +23 min
  • Sat 31 Oct Max en route +24 min · last fix heading to Breda +23 min
  • Sat 24 Oct Max en route +7 min · last fix heading to Breda +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 19
  • 3–10 min 5% · 1
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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