Train NS Int 9219 Brussel-Zuid – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 07:44 from Brussel-Zuid · Fri 6 Nov

Next departure 07:44 today · Brussel-Zuid
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 16 full · 11 partial · 2 no data
On-time · 90 days
88%
29/33 runs under 3 min
RT coverage: 22 full · 11 partial · 54 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: +2 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

  • Wed 7 Oct Max en route +40 min · last fix heading to Breda +40 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Breda +5 min
  • Tue 6 Oct Max en route +6 min · last fix heading to Breda +4 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Breda +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 29
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 80% W n=5
  • 83% T n=6
  • 100% F n=6
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

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