Train NS Int 9536 Lelystad Centrum – Brussel-Zuid

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

Running now · updated 11:48

Heading to Brussel-Zuid 0 min

Estimated arrival at Brussel-Zuid 14:11 · 87 km/h

  1. Lelystad Centrum11:23
  2. Almere Buiten11:34
  3. Almere Centrum11:39
  4. Schiphol Airport12:09
  5. Rotterdam Centraal12:38
  6. Antwerpen-Centraal13:26
  7. Brussel-Zuid14:11

Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 21 runs arrived on time.

On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 partial · 9 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 29 full · 3 partial · 56 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

  • Sun 18 Oct Max en route +13 min · last fix heading to Rotterdam Centraal +13 min
  • Sat 14 Nov Max en route +10 min · last fix heading to Rotterdam Centraal +10 min
  • Mon 9 Nov Max en route +10 min · last fix heading to Rotterdam Centraal +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 3% · 1
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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