Train NS Int 9544 Lelystad Centrum – Brussel-Zuid

Lelystad Centrum 13:23 → Brussel-Zuid 16:03 Daily 2 h 40 min · 8 stops NS Int

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 16:04 0 min

  1. Lelystad Centrum13:23
  2. Almere Buiten13:34
  3. Almere Centrum13:39
  4. Schiphol Airport14:10
  5. Rotterdam Centraal14:39
  6. Antwerpen-Centraal15:26
  7. Brussel-Zuid16:03

Next service: tomorrow 13:23 from Lelystad Centrum · Thu 12 Nov

Next departure 13:23 tomorrow · Lelystad Centrum
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 15 full · 1 partial · 14 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

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

Worst days

  • Sun 11 Oct Max en route +19 min · last fix heading to Rotterdam Centraal +15 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Rotterdam Centraal +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
13:23on time on time
13:34≈ on time ≈ on time
13:39 / 13:41≈ on time ≈ on time
14:02 / 14:04≈ on time ≈ +1 min
14:10 / 14:12≈ on time ≈ +1 min
14:39 / 14:42≈ on time ≈ +1 min
15:26 / 15:29≈ on time ≈ +2 min
16:03on time +2 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
Wed 11 NovRotterdam Centraal 16:04Partial coverage0 min—
Tue 10 NovRotterdam Centraal 16:120 min—
Mon 9 NovRotterdam Centraal 16:130 min—
Sun 8 NovBreda 16:09+2 min+2 min
Sat 7 NovBreda 15:070 min—
Fri 6 NovRotterdam Centraal 16:12No data—
Thu 5 NovRotterdam Centraal 16:13No data—
Wed 4 NovRotterdam Centraal 16:130 min—
Tue 3 NovRotterdam Centraal 16:52No data—
Mon 2 NovRotterdam Centraal 16:13No data—
Sun 1 NovRotterdam Centraal 16:050 min—
Sat 31 OctRotterdam Centraal 16:040 min—
Fri 30 OctRotterdam Centraal 14:56No data—
Thu 29 OctRotterdam Centraal 14:570 min—
Wed 28 OctRotterdam Centraal 16:120 min—
Tue 27 OctRotterdam Centraal 16:130 min—
Mon 26 OctRotterdam Centraal 16:12No data—
Sun 25 OctRotterdam Centraal 16:04No data—
Sat 24 OctRotterdam Centraal 16:040 min—
Fri 23 OctRotterdam Centraal 15:13No data—
Thu 22 OctRotterdam Centraal 16:12No data—
Wed 21 OctRotterdam Centraal 16:46No data—
Tue 20 OctRotterdam Centraal 14:570 min—
Mon 19 OctRotterdam Centraal 16:130 min—
Sun 18 OctRotterdam Centraal 16:00+9 min+9 min
Sat 17 OctRotterdam Centraal 15:47No data—
Fri 16 OctRotterdam Centraal 16:12No data—
Thu 15 OctRotterdam Centraal 16:12No data—
Wed 14 OctRotterdam Centraal 16:13No data—
Tue 13 OctRotterdam Centraal 16:120 min—