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