Train NS Int 9527 Brussel-Zuid – Lelystad Centrum

Brussel-Zuid 07:49 → Lelystad Centrum 10:38 Daily 2 h 49 min · 8 stops NS Int

✓ Today’s run finished

Today, last fix heading to Almere Buiten at 10:40 0 min

  1. Brussel-Zuid07:49
  2. Antwerpen-Centraal08:23
  3. Rotterdam Centraal09:17
  4. Amsterdam Zuid09:54
  5. Almere Centrum10:17
  6. Almere Buiten10:26
  7. Lelystad Centrum10:38

Next service: tomorrow 07:49 from Brussel-Zuid · Tue 27 Oct

Next departure 07:49 tomorrow · Brussel-Zuid
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 13 full · 1 partial · 13 no data
On-time · 90 days
71%
10/14 runs under 3 min
RT coverage: 13 full · 1 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +11 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 +16 min · last fix heading to Amsterdam Zuid +16 min
  • Thu 8 Oct Max en route +12 min · last fix heading to Almere Buiten +12 min
  • Sat 24 Oct Max en route +8 min · last fix heading to Almere Buiten +8 min
  • Sat 17 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 10
  • 3–10 min 14% · 2
  • 10–30 min 14% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=1
  • 0% T n=1
  • 100% F n=2
  • 33% S n=3
  • 50% S n=2

Stops and timetable

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

StopSched.
07:49
08:23 / 08:35
09:17 / 09:21
09:47 / 09:48
09:54 / 09:56
10:17 / 10:21
10:26
10:38

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.

Recent runs

DateLast stopFinalMax
Mon 26 OctAlmere Buiten 10:40Partial coverage0 min—
Sun 25 OctAmsterdam Zuid 10:13No data—
Sat 24 OctAlmere Buiten 10:53+8 min+8 min
Fri 23 OctAlmere Buiten 10:390 min—
Thu 22 OctAlmere Buiten 11:20No data—
Wed 21 OctSchiphol Airport 10:03No data—
Tue 20 OctAmsterdam Zuid 10:100 min—
Mon 19 OctAlmere Buiten 10:390 min—
Sun 18 OctAmsterdam Zuid 10:31+16 min+16 min
Sat 17 OctAmsterdam Zuid 10:17+3 min+4 min
Fri 16 OctAlmere Buiten 10:41No data—
Thu 15 OctRotterdam Centraal 10:58No data—
Wed 14 OctAlmere Buiten 10:46No data—
Tue 13 OctAlmere Buiten 10:470 min—
Sun 11 OctAmsterdam Zuid 10:150 min—
Sat 10 OctAlmere Buiten 10:39+2 min+2 min
Fri 9 OctAlmere Buiten 10:400 min+1 min
Thu 8 OctAlmere Buiten 11:00+12 min+12 min
Wed 7 OctAlmere Buiten 12:000 min—
Tue 6 OctAlmere Buiten 10:41+1 min+2 min
Mon 5 OctAlmere Buiten 10:39No data—
Fri 2 OctAlmere Buiten 10:39No data—
Thu 1 OctAlmere Buiten 10:39No data—
Wed 30 SeptAlmere Buiten 10:40No data—
Tue 29 SeptAlmere Buiten 10:43No data—
Mon 28 SeptAlmere Buiten 10:39No data—
Sun 27 SeptAmsterdam Bijlmer ArenA 10:20No data—
Sat 26 SeptAmsterdam Bijlmer ArenA 10:55No data—
Fri 25 SeptAlmere Buiten 10:39No data—
Thu 24 SeptAlmere Buiten 10:39No data—