Train NS Int 9539 Brussel-Zuid – Breda

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 10:57 from Brussel-Zuid · Sun 8 Nov

Next departure 10:57 today · Brussel-Zuid
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 14 full · 1 partial · 14 no data
On-time · 90 days
81%
17/21 runs under 3 min
RT coverage: 20 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 9 Oct Max en route +25 min · last fix heading to Almere Buiten +24 min
  • Wed 4 Nov Max en route +22 min · last fix heading to Almere Buiten +22 min
  • Wed 7 Oct Max en route +12 min · last fix heading to Almere Buiten +11 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Amsterdam Zuid +7 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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