Train NS Int 9560 Lelystad Centrum – Brussel-Zuid

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 17:23 from Lelystad Centrum · Sat 7 Nov

Next departure 17:23 today · Lelystad Centrum
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 14 full · 3 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 partial · 67 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

  • Fri 23 Oct Max en route +46 min · last fix heading to Rotterdam Centraal +46 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 95% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
17:23on time on time
17:34≈ on time ≈ on time
17:39 / 17:41≈ on time ≈ on time
18:01 / 18:03≈ on time ≈ on time
18:09 / 18:11≈ on time ≈ on time
18:38 / 18:42≈ on time ≈ on time
19:26 / 19:37≈ on time ≈ on time
20: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
Fri 6 NovRotterdam Centraal 20:09Partial coverage0 min—
Thu 5 NovSchiphol Airport 19:09No data—
Wed 4 NovSchiphol Airport 19:09No data—
Tue 3 NovSchiphol Airport 20:12No data—
Mon 2 NovAmsterdam Zuid 20:120 min—
Sun 1 NovRotterdam Centraal 18:540 min—
Sat 31 OctRotterdam Centraal 20:040 min—
Fri 30 OctRotterdam Centraal 20:12No data—
Thu 29 OctAlmere Centrum 20:120 min—
Wed 28 OctSchiphol Airport 20:120 min—
Tue 27 OctAmsterdam Zuid 20:130 min—
Mon 26 OctAmsterdam Zuid 20:35No data—
Sun 25 OctRotterdam Centraal 20:04No data—
Sat 24 OctRotterdam Centraal 20:040 min—
Fri 23 OctRotterdam Centraal 20:52Partial coverage+46 min+46 min
Thu 22 OctRotterdam Centraal 20:13No data—
Wed 21 OctSchiphol Airport 20:13No data—
Tue 20 OctRotterdam Centraal 20:120 min—
Mon 19 OctRotterdam Centraal 20:130 min—
Sun 18 OctRotterdam Centraal 19:420 min—
Sat 17 OctRotterdam Centraal 19:43No data—
Fri 16 OctRotterdam Centraal 20:12No data—
Thu 15 OctAmsterdam Zuid 20:40No data—
Wed 14 OctRotterdam Centraal 20:12No data—
Tue 13 Oct— 20:130 min—
Mon 12 OctRotterdam Centraal 20:120 min—
Sun 11 OctRotterdam Centraal 20:040 min+3 min
Sat 10 OctRotterdam Centraal 20:040 min—
Fri 9 OctSchiphol Airport 20:12Partial coverage0 min—
Thu 8 OctAlmere Centrum 20:120 min—