Train NS Int 9535 Brussel-Zuid – Breda

Brussel-Zuid 09:57 → Breda 11:18 Daily 1 h 21 min · 3 stops NS Int

Running now · updated 10:19

Heading to Breda 0 min

Estimated arrival at Breda 11:18 · 160 km/h

  1. Brussel-Zuid09:57
  2. Antwerpen-Centraal10:31
  3. Breda11:18

Today it is running no worse than usual: typical arrival delay is 0 min; 88% of the last 16 runs arrived on time.

On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 15 full · 1 partial · 13 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 19 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Breda, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +13 min · last fix heading to Almere Buiten +12 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Rotterdam Centraal +5 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 10% · 2
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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 10Today
09:57on time on time
10:31 / 10:36≈ on time ≈ +2 min
11:18on 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
Sat 7 NovRoosendaal 10:14Partial coverage0 min—
Fri 6 NovAlmere Buiten 12:39No data—
Thu 5 NovAlmere Buiten 12:39No data—
Wed 4 NovAlmere Buiten 12:39+1 min+1 min
Tue 3 NovAlmere Buiten 13:040 min—
Mon 2 NovAlmere Buiten 12:390 min—
Sun 1 NovAmsterdam Zuid 12:150 min—
Sat 31 OctAlmere Buiten 12:40+1 min+2 min
Fri 30 OctAlmere Buiten 12:39No data—
Thu 29 OctAlmere Buiten 12:400 min—
Wed 28 OctAlmere Buiten 13:200 min—
Tue 27 OctAlmere Buiten 12:56No data—
Mon 26 OctAlmere Buiten 13:00No data—
Sun 25 OctSchiphol Airport 13:08No data—
Sat 24 OctAlmere Buiten 12:400 min+2 min
Fri 23 OctAlmere Buiten 13:00No data—
Thu 22 OctAlmere Buiten 13:20No data—
Wed 21 Oct— 11:29No data—
Tue 20 OctAlmere Buiten 12:400 min—
Mon 19 OctAlmere Buiten 12:570 min—
Sun 18 OctRotterdam Centraal 12:30+5 min+5 min
Sat 17 OctAmsterdam Zuid 12:15No data—
Fri 16 OctAlmere Buiten 12:41No data—
Thu 15 OctAlmere Buiten 12:41No data—
Wed 14 OctAlmere Buiten 12:41No data—
Tue 13 OctAlmere Buiten 12:450 min—
Sun 11 OctAmsterdam Zuid 12:17+4 min+4 min
Sat 10 OctAlmere Buiten 12:390 min—
Fri 9 OctRotterdam Centraal 12:380 min—
Thu 8 OctAlmere Buiten 13:02+12 min+13 min