Train NS Int 9523 Brussel-Zuid – Lelystad Centrum
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 06:49 from Brussel-Zuid · Thu 5 Nov
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 7 Oct Max en route +29 min · last fix heading to Almere Buiten +29 min
- Thu 8 Oct Max en route +25 min · last fix heading to Almere Buiten +24 min
- Tue 6 Oct Max en route +7 min · last fix heading to Almere Buiten +6 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 23
- 3–10 min 4% · 1
- 10–30 min 8% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 75% T n=4
- 80% W n=5
- 75% T n=4
- 100% F n=3
- 100% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 26 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:49 | on time | on time | |
| 07:23 / 07:35 | ≈ on time | ≈ on time | |
| 08:17 / 08:21 | ≈ on time | ≈ +1 min | |
| 08:47 / 08:48 | ≈ on time | ≈ +1 min | |
| 08:54 / 08:56 | ≈ on time | ≈ +1 min | |
| 09:17 / 09:20 | ≈ on time | ≈ +2 min | |
| 09:25 | ≈ on time | ≈ +2 min | |
| 09:36 | on time | +2 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Almere Buiten 09:39Partial coverage | 0 min | +2 min |
| Tue 3 Nov | Almere Buiten 09:39Partial coverage | 0 min | — |
| Mon 2 Nov | Almere Buiten 09:39 | No data | — |
| Sun 1 Nov | Amsterdam Zuid 09:13 | 0 min | — |
| Sat 31 Oct | Amsterdam Zuid 09:14 | 0 min | — |
| Fri 30 Oct | Rotterdam Centraal 09:42 | No data | — |
| Thu 29 Oct | Almere Buiten 10:12Partial coverage | 0 min | — |
| Wed 28 Oct | Almere Buiten 09:39Partial coverage | 0 min | — |
| Tue 27 Oct | Almere Buiten 09:39Partial coverage | 0 min | — |
| Mon 26 Oct | Almere Buiten 10:00Partial coverage | 0 min | — |
| Sun 25 Oct | Amsterdam Zuid 09:14 | No data | — |
| Sat 24 Oct | Amsterdam Zuid 09:16 | +2 min | +2 min |
| Fri 23 Oct | Almere Buiten 09:39 | 0 min | — |
| Thu 22 Oct | Almere Buiten 09:39Partial coverage | 0 min | — |
| Wed 21 Oct | Almere Buiten 10:26Partial coverage | 0 min | — |
| Tue 20 Oct | Almere Buiten 10:09 | No data | — |
| Mon 19 Oct | Almere Buiten 09:39Partial coverage | 0 min | — |
| Sun 18 Oct | Amsterdam Zuid 09:17 | +3 min | +4 min |
| Sat 17 Oct | Amsterdam Zuid 09:14 | 0 min | — |
| Fri 16 Oct | Almere Buiten 09:39 | 0 min | — |
| Thu 15 Oct | Almere Buiten 10:58 | 0 min | — |
| Wed 14 Oct | Almere Buiten 09:39Partial coverage | 0 min | — |
| Tue 13 Oct | Almere Buiten 10:16Partial coverage | 0 min | — |
| Sun 11 Oct | Amsterdam Zuid 09:14 | 0 min | — |
| Sat 10 Oct | Amsterdam Zuid 09:12 | 0 min | — |
| Fri 9 Oct | Almere Buiten 09:40 | 0 min | — |
| Thu 8 Oct | Almere Buiten 10:26Partial coverage | +24 min | +25 min |
| Wed 7 Oct | Almere Buiten 10:34Partial coverage | +29 min | +29 min |
| Tue 6 Oct | Almere Buiten 09:49Partial coverage | +6 min | +7 min |
| Mon 5 Oct | Almere Buiten 10:19 | No data | — |