Train NS Int 9227 Brussel-Zuid – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Breda at 11:48 +10 min

  1. Brussel-Zuid09:44
  2. Brussel-Noord09:53
  3. Brussels Airport-Zaventem10:07
  4. Antwerpen-Berchem10:36
  5. Antwerpen-Centraal10:42
  6. Breda11:19
  7. Rotterdam Centraal11:50

Next service: tomorrow 09:44 from Brussel-Zuid · Fri 13 Nov

Next departure 09:44 tomorrow · Brussel-Zuid
On-time · 30 days
69%
9/13 runs under 3 min
RT coverage: 5 full · 8 partial · 15 no data
On-time · 90 days
72%
13/18 runs under 3 min
RT coverage: 10 full · 8 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +14 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

  • Sat 24 Oct Max en route +21 min · last fix heading to Breda +20 min
  • Mon 9 Nov Max en route +16 min · last fix heading to Breda +14 min
  • Wed 11 Nov Max en route +13 min · last fix heading to Breda +13 min
  • Thu 12 Nov Max en route +10 min · last fix heading to Breda +10 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Breda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 72% · 13
  • 3–10 min 11% · 2
  • 10–30 min 17% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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