Train NS Int 9543 Brussel-Zuid – Lelystad Centrum

Brussel-Zuid 11:49 → Lelystad Centrum 14:36 Daily 2 h 47 min · 8 stops NS Int

✓ Today’s run finished

Today, last fix heading to Almere Buiten at 14:39 No data

  1. Brussel-Zuid11:49
  2. Antwerpen-Centraal12:23
  3. Rotterdam Centraal13:17
  4. Amsterdam Zuid13:54
  5. Almere Centrum14:17
  6. Almere Buiten14:25
  7. Lelystad Centrum14:36

Next service: tomorrow 11:49 from Brussel-Zuid · Sat 7 Nov

Next departure 11:49 tomorrow · Brussel-Zuid
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 10 full · 4 partial · 16 no data
On-time · 90 days
76%
13/17 runs under 3 min
RT coverage: 10 full · 7 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +13 min

Last 30 days

Arrival delay at Lelystad Centrum, 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 +47 min · last fix heading to Amsterdam Zuid +47 min
  • Fri 9 Oct Max en route +17 min · last fix heading to Almere Buiten +16 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Almere Buiten +5 min
  • Sun 11 Oct Max en route +3 min · last fix heading to Amsterdam Zuid +3 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 76% · 13
  • 3–10 min 12% · 2
  • 10–30 min 6% · 1
  • 30+ min 6% · 1

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 67% W n=3
  • 100% T n=1
  • 0% F n=1
  • 100% S n=3
  • 33% 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
11:49on time on time
12:23 / 12:35≈ on time ≈ +4 min
13:17 / 13:21≈ on time ≈ +10 min
13:47 / 13:48≈ on time ≈ +14 min
13:54 / 13:56≈ on time ≈ +14 min
14:17 / 14:20≈ on time ≈ +17 min
14:25≈ on time ≈ +18 min
14:36on time +19 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 6 NovAlmere Buiten 14:39No data—
Thu 5 NovAlmere Centrum 15:39No data—
Wed 4 NovAlmere Buiten 14:48Partial coverage+5 min+5 min
Tue 3 NovAlmere Buiten 14:39No data—
Mon 2 NovAlmere Buiten 14:39No data—
Sun 1 NovAmsterdam Zuid 14:16+1 min+1 min
Sat 31 OctAlmere Buiten 14:390 min—
Fri 30 OctAlmere Buiten 14:39No data—
Thu 29 OctAlmere Buiten 14:40No data—
Wed 28 OctAlmere Buiten 14:400 min—
Tue 27 OctAlmere Buiten 15:060 min—
Mon 26 OctAlmere Buiten 14:41No data—
Sun 25 OctAmsterdam Zuid 15:00No data—
Sat 24 OctAlmere Buiten 14:390 min—
Fri 23 OctAlmere Buiten 14:41No data—
Thu 22 OctAlmere Buiten 14:39No data—
Wed 21 OctAlmere Buiten 15:42No data—
Tue 20 OctAlmere Buiten 14:40Partial coverage0 min—
Mon 19 OctAlmere Buiten 14:39Partial coverage0 min—
Sun 18 OctAmsterdam Zuid 15:05+47 min+47 min
Sat 17 OctAmsterdam Zuid 14:16No data—
Fri 16 OctAlmere Buiten 15:20No data—
Thu 15 OctAlmere Buiten 14:41No data—
Wed 14 OctAlmere Buiten 14:41No data—
Tue 13 OctAlmere Centrum 15:180 min—
Mon 12 Oct— 13:19No data—
Sun 11 OctAmsterdam Zuid 14:16+3 min+3 min
Sat 10 OctAlmere Buiten 14:500 min+10 min
Fri 9 OctAlmere Buiten 15:09+16 min+17 min
Thu 8 OctAlmere Buiten 14:39Partial coverage0 min—