Train NS Int 9555 Brussel-Zuid – Lelystad Centrum

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 14:49 from Brussel-Zuid · Thu 19 Nov

Next departure 14:49 today · Brussel-Zuid
On-time · 30 days
67%
14/21 runs under 3 min
RT coverage: 10 full · 11 partial · 8 no data
On-time · 90 days
72%
23/32 runs under 3 min
RT coverage: 14 full · 18 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+17min
9 in 10 runs arrive with less than this
30 days: +18 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

  • Wed 4 Nov Max en route +30 min · last fix heading to Almere Centrum +30 min
  • Fri 6 Nov Max en route +29 min · last fix heading to Almere Buiten +29 min
  • Sun 15 Nov Max en route +39 min · last fix heading to Amsterdam Zuid +18 min
  • Mon 26 Oct Max en route +18 min · last fix heading to Almere Buiten +18 min
  • Sat 14 Nov Max en route +9 min · last fix heading to Almere Buiten +9 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 72% · 23
  • 3–10 min 16% · 5
  • 10–30 min 9% · 3
  • 30+ min 3% · 1

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 80% W n=5
  • 100% T n=2
  • 33% F n=3
  • 80% S n=5
  • 20% 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 10
14:49on time on time
15:23 / 15:35≈ +1 min ≈ +3 min
16:17 / 16:21≈ +2 min ≈ +8 min
16:47 / 16:48≈ +2 min ≈ +11 min
16:54 / 16:56≈ +2 min ≈ +11 min
17:17 / 17:20≈ +3 min ≈ +13 min
17:25≈ +3 min ≈ +14 min
17:36+3 min +15 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
Wed 18 NovAlmere Buiten 17:39Partial coverage0 min—
Tue 17 NovAlmere Buiten 17:39Partial coverage0 min—
Mon 16 NovAlmere Buiten 17:47Partial coverage0 min+13 min
Sun 15 NovAmsterdam Zuid 18:14+18 min+39 min
Sat 14 NovAlmere Buiten 17:49+9 min+9 min
Fri 13 NovAlmere Buiten 17:44+3 min+5 min
Thu 12 NovAlmere Buiten 17:39Partial coverage0 min—
Wed 11 NovAlmere Buiten 17:39+3 min+3 min
Tue 10 NovSchiphol Airport 17:02Partial coverage0 min—
Mon 9 NovAlmere Buiten 17:39Partial coverage0 min—
Sun 8 NovRoosendaal 16:34+7 min+7 min
Sat 7 NovRoosendaal 16:19+1 min+1 min
Fri 6 NovAlmere Buiten 18:19+29 min+29 min
Thu 5 NovAlmere Buiten 18:18No data—
Wed 4 NovAlmere Centrum 18:18Partial coverage+30 min+30 min
Tue 3 NovAlmere Buiten 18:19Partial coverage0 min—
Mon 2 NovAlmere Buiten 17:39Partial coverage0 min—
Sun 1 NovAmsterdam Zuid 17:140 min—
Sat 31 OctAlmere Buiten 17:390 min—
Fri 30 OctAlmere Buiten 17:40No data—
Thu 29 OctAlmere Buiten 17:38No data—
Wed 28 OctAlmere Buiten 17:39Partial coverage0 min—
Tue 27 OctAlmere Buiten 17:44No data—
Mon 26 OctAlmere Buiten 18:13Partial coverage+18 min+18 min
Sun 25 OctAmsterdam Zuid 17:18No data—
Sat 24 OctAlmere Buiten 17:390 min—
Fri 23 OctAlmere Buiten 17:39No data—
Thu 22 OctAlmere Buiten 17:44No data—
Wed 21 OctAlmere Buiten 18:21No data—
Tue 20 OctAlmere Buiten 17:39Partial coverage0 min—