Train NS Int 9268 Rotterdam Centraal → Brussel-Zuid
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).
An alert on this phone or computer when the 9268 is 5 min or more late, every day it runs. No account, no email.
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
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 21:10 | on 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:39 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Breda 21:54Partial coverage | 0 min | — |
| Sun 15 Nov | Roosendaal 21:59 | 0 min | — |
| Sat 14 Nov | Roosendaal 21:54 | 0 min | — |
| Sun 8 Nov | Roosendaal 21:54 | 0 min | — |
| Sat 7 Nov | Roosendaal 21:54 | 0 min | — |
| Sun 1 Nov | Breda 21:54 | 0 min | — |
| Sat 31 Oct | Breda 21:56 | No data | — |
| Sat 24 Oct | Breda 21:57 | 0 min | — |
| Sun 18 Oct | Breda 21:58 | 0 min | — |
| Sat 17 Oct | Breda 21:56 | 0 min | — |
| Sun 11 Oct | Breda 21:56 | 0 min | — |
| Sat 10 Oct | Breda 21:56 | +2 min | +2 min |
| Sat 3 Oct | Roosendaal 21:55 | No data | — |
| Sun 27 Sept | Breda 21:56 | No data | — |
| Sat 26 Sept | Breda 21:56 | No data | — |
| Sun 20 Sept | Breda 21:57 | No data | — |
| Sat 19 Sept | Breda 21:56 | No data | — |
| Sun 13 Sept | Breda 21:59 | No data | — |
| Sat 12 Sept | Breda 21:57 | No data | — |
| Sun 6 Sept | Breda 21:57 | No data | — |
| Sat 5 Sept | Breda 21:56 | No data | — |
| Sun 30 Aug | Breda 21:57 | No data | — |
| Sat 29 Aug | Breda 21:56 | No data | — |