Train NS Int 9563 Antwerpen-Centraal – Lelystad Centrum

Antwerpen-Centraal 17:08 → Lelystad Centrum 19: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 17:08 from Antwerpen-Centraal · Sun 15 Nov

Next departure 17:08 today · Antwerpen-Centraal
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 21 full · 1 partial · 7 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 30 full · 1 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 6 Nov Max en route +35 min · last fix heading to Rotterdam Centraal +35 min
  • Mon 5 Oct Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 3% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
17:08on time on time
18:19 / 18:22≈ on time ≈ +1 min
18:48 / 18:50≈ on time ≈ +2 min
18:56 / 18:58≈ on time ≈ +2 min
19:17 / 19:20≈ on time ≈ +2 min
19:25≈ on time ≈ +2 min
19:36on time +3 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 19:39Partial coverage0 min+6 min
Fri 13 NovSchiphol Airport 19:040 min—
Thu 12 NovRotterdam Centraal 19:390 min—
Wed 11 Nov— 19:370 min—
Tue 10 NovRotterdam Centraal 18:540 min—
Mon 9 Nov— 19:370 min—
Sun 8 NovUtrecht Centraal 19:440 min+4 min
Sat 7 NovUtrecht Centraal 19:440 min+3 min
Fri 6 NovRotterdam Centraal 20:24+35 min+35 min
Thu 5 Nov— 19:370 min—
Wed 4 Nov— 19:380 min—
Tue 3 Nov— 20:190 min—
Mon 2 Nov— 19:390 min—
Sun 1 NovAmsterdam Zuid 19:140 min—
Sat 31 OctAlmere Buiten 19:390 min—
Fri 30 OctSchiphol Airport 19:04No data—
Thu 29 Oct— 19:37+1 min+2 min
Wed 28 Oct— 20:000 min—
Tue 27 Oct— 19:38No data—
Mon 26 Oct— 19:370 min—
Sun 25 OctAmsterdam Zuid 19:22No data—
Sat 24 OctAlmere Buiten 19:410 min—
Fri 23 OctAlmere Buiten 19:42+2 min+3 min
Thu 22 OctRotterdam Centraal 19:38No data—
Wed 21 OctRotterdam Centraal 19:38No data—
Tue 20 OctRotterdam Centraal 18:35No data—
Mon 19 OctRotterdam Centraal 19:530 min—
Sun 18 OctAmsterdam Zuid 19:16+3 min+3 min
Sat 17 OctAmsterdam Zuid 19:14No data—
Fri 16 OctAlmere Buiten 19:39No data—