Train NS Int 9531 Antwerpen-Centraal – Lelystad Centrum

Antwerpen-Centraal 09:08 → Lelystad Centrum 11:36 Daily 2 h 28 min · 7 stops NS Int

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 09:08 from Antwerpen-Centraal · Sun 15 Nov

Next departure 09:08 today · Antwerpen-Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 17 full · 1 partial · 11 no data
On-time · 90 days
84%
21/25 runs under 3 min
RT coverage: 24 full · 1 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Mon 9 Nov Max en route +48 min · last fix heading to Almere Centrum +46 min
  • Wed 7 Oct Max en route +39 min · last fix heading to Almere Buiten +38 min
  • Sat 24 Oct Max en route +15 min · last fix heading to Almere Buiten +15 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Almere Buiten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 21
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 8% · 2

On-time by weekday

  • 50% M n=2
  • 100% T n=5
  • 75% W n=4
  • 100% T n=2
  • 100% F n=2
  • 67% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 25 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
09:08on time on time
10:19 / 10:22≈ on time ≈ +6 min
10:48 / 10:50≈ on time ≈ +8 min
10:56 / 10:58≈ on time ≈ +8 min
11:17 / 11:20≈ on time ≈ +10 min
11:25≈ on time ≈ +11 min
11:36on time +12 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
Sat 14 NovAlmere Buiten 11:39Partial coverage0 min+1 min
Fri 13 NovAlmere Buiten 11:39+2 min+2 min
Thu 12 NovAlmere Buiten 11:39+1 min+2 min
Wed 11 NovAlmere Buiten 11:390 min—
Tue 10 NovSchiphol Airport 11:030 min—
Mon 9 NovAlmere Centrum 12:38+46 min+48 min
Sun 8 NovRoosendaal 10:190 min—
Sat 7 NovRoosendaal 10:190 min—
Fri 6 NovAlmere Buiten 12:19No data—
Thu 5 NovAlmere Buiten 11:39No data—
Wed 4 NovSchiphol Airport 11:04+3 min+3 min
Tue 3 NovAlmere Buiten 11:40No data—
Mon 2 NovAlmere Buiten 11:39No data—
Sun 1 NovAmsterdam Zuid 11:150 min—
Sat 31 OctSchiphol Airport 11:06+2 min+3 min
Fri 30 OctAlmere Buiten 11:46No data—
Thu 29 OctAlmere Buiten 11:39No data—
Wed 28 OctAlmere Buiten 11:390 min—
Tue 27 OctAlmere Buiten 11:420 min—
Mon 26 OctAlmere Buiten 11:39No data—
Sun 25 OctAmsterdam Zuid 11:14No data—
Sat 24 OctAlmere Buiten 12:07+15 min+15 min
Fri 23 OctAlmere Buiten 12:18No data—
Thu 22 OctAlmere Buiten 11:39No data—
Wed 21 OctRotterdam Centraal 10:35No data—
Tue 20 OctAlmere Buiten 11:400 min—
Mon 19 OctAlmere Buiten 11:560 min—
Sun 18 OctAmsterdam Zuid 11:17+3 min+3 min
Sat 17 OctAmsterdam Zuid 11:270 min—
Fri 16 OctAlmere Buiten 11:39No data—