Train NS Int 9520 Lelystad Centrum – Brussel-Zuid

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 10:13 0 min

  1. Lelystad Centrum07:23
  2. Almere Buiten07:34
  3. Almere Centrum07:39
  4. Schiphol Airport08:10
  5. Rotterdam Centraal08:39
  6. Antwerpen-Centraal09:26
  7. Brussel-Zuid10:11

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

Next departure 07:23 tomorrow · Lelystad Centrum
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 16 full · 8 partial · 6 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 16 full · 9 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sat 17 Oct Max en route +15 min · last fix heading to Rotterdam Centraal +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=3
  • 100% T n=4
  • 100% F n=3
  • 75% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 25 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
07:23on time on time
07:34≈ on time ≈ on time
07:39 / 07:41≈ on time ≈ on time
08:02 / 08:04≈ on time ≈ on time
08:10 / 08:12≈ on time ≈ on time
08:39 / 08:42≈ on time ≈ on time
09:26 / 09:37≈ on time ≈ on time
10:11on 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

DateLast stopFinalMax
Thu 5 NovRotterdam Centraal 10:13Partial coverage0 min—
Wed 4 NovRotterdam Centraal 09:090 min—
Tue 3 NovRotterdam Centraal 10:13Partial coverage0 min—
Mon 2 NovRotterdam Centraal 10:130 min—
Sun 1 NovRotterdam Centraal 10:040 min—
Sat 31 OctRotterdam Centraal 10:040 min—
Fri 30 OctRotterdam Centraal 10:120 min—
Thu 29 OctRotterdam Centraal 10:12Partial coverage0 min—
Wed 28 OctRotterdam Centraal 10:120 min—
Tue 27 OctRotterdam Centraal 10:13Partial coverage0 min—
Mon 26 OctRotterdam Centraal 10:120 min—
Sun 25 OctRotterdam Centraal 10:04No data—
Sat 24 OctRotterdam Centraal 10:040 min—
Fri 23 OctRotterdam Centraal 10:120 min—
Thu 22 OctRotterdam Centraal 10:12No data—
Wed 21 OctRotterdam Centraal 10:12No data—
Tue 20 OctAmsterdam Zuid 09:39Partial coverage0 min—
Mon 19 OctRotterdam Centraal 10:120 min—
Sun 18 OctRotterdam Centraal 09:420 min—
Sat 17 OctRotterdam Centraal 10:12+15 min+15 min
Fri 16 OctRotterdam Centraal 10:12No data—
Thu 15 OctRotterdam Centraal 10:58Partial coverage0 min—
Wed 14 OctRotterdam Centraal 10:12No data—
Tue 13 OctRotterdam Centraal 10:12Partial coverage0 min—
Mon 12 OctRotterdam Centraal 10:13No data—
Sun 11 OctRotterdam Centraal 10:040 min—
Sat 10 OctRotterdam Centraal 10:040 min—
Fri 9 OctRotterdam Centraal 10:130 min—
Thu 8 OctRotterdam Centraal 10:12Partial coverage0 min—
Wed 7 OctRotterdam Centraal 10:130 min—