Train NS Int 9540 Lelystad Centrum – Brussel-Zuid

Lelystad Centrum 12:23 → Brussel-Zuid 15:11 Daily 2 h 48 min · 8 stops NS Int

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 14:22 No data

  1. Lelystad Centrum12:23
  2. Almere Buiten12:34
  3. Almere Centrum12:39
  4. Schiphol Airport13:10
  5. Rotterdam Centraal13:39
  6. Antwerpen-Centraal14:26
  7. Brussel-Zuid15:11

Next service: tomorrow 12:23 from Lelystad Centrum · Fri 6 Nov

Next departure 12:23 tomorrow · Lelystad Centrum
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 7 full · 8 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 8 full · 9 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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 18 Oct Max en route +10 min · last fix heading to Rotterdam Centraal +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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