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