Train NS Int 9551 Brussel-Zuid – Lelystad Centrum
It has not run yet today
Last recorded run: Friday 13 November +40 min
Next service: tomorrow 13:49 from Brussel-Zuid · Sun 15 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 13 Nov Max en route +40 min · last fix heading to Almere Buiten +40 min
- Wed 4 Nov Max en route +38 min · last fix heading to Almere Centrum +38 min
- Sat 24 Oct Max en route +21 min · last fix heading to Almere Buiten +21 min
- Thu 8 Oct Max en route +12 min · last fix heading to Almere Buiten +11 min
- Sun 18 Oct Max en route +11 min · last fix heading to Amsterdam Zuid +11 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 72% · 18
- 3–10 min 8% · 2
- 10–30 min 12% · 3
- 30+ min 8% · 2
On-time by weekday
- 100% M n=3
- 80% T n=5
- 75% W n=4
- 67% T n=3
- 50% F n=2
- 50% 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, 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 13:49 | on time | on time | |
| 14:23 / 14:35 | ≈ on time | ≈ +2 min | |
| 15:17 / 15:22 | ≈ on time | ≈ +6 min | |
| 15:48 / 15:50 | ≈ on time | ≈ +8 min | |
| 15:56 / 15:58 | ≈ on time | ≈ +9 min | |
| 16:17 / 16:20 | ≈ on time | ≈ +10 min | |
| 16:25 | ≈ on time | ≈ +11 min | |
| 16:36 | on time | +11 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 13 Nov | Almere Buiten 17:19Partial coverage | +40 min | +40 min |
| Thu 12 Nov | Almere Buiten 16:39 | 0 min | — |
| Wed 11 Nov | Almere Buiten 16:39 | 0 min | — |
| Tue 10 Nov | Schiphol Airport 16:08 | +5 min | +6 min |
| Mon 9 Nov | Almere Buiten 16:39 | 0 min | +1 min |
| Sun 8 Nov | Roosendaal 15:19 | 0 min | — |
| Sat 7 Nov | Roosendaal 15:34 | +8 min | +8 min |
| Fri 6 Nov | Almere Buiten 17:08 | No data | — |
| Thu 5 Nov | Almere Buiten 16:39 | No data | — |
| Wed 4 Nov | Almere Centrum 17:39 | +38 min | +38 min |
| Tue 3 Nov | Almere Buiten 17:19 | No data | — |
| Mon 2 Nov | Almere Buiten 17:08 | No data | — |
| Sun 1 Nov | Amsterdam Zuid 16:17 | +2 min | +2 min |
| Sat 31 Oct | Almere Buiten 16:39 | 0 min | — |
| Fri 30 Oct | Almere Buiten 16:40 | No data | — |
| Thu 29 Oct | Almere Buiten 16:41 | 0 min | — |
| Wed 28 Oct | Almere Buiten 16:41 | 0 min | — |
| Tue 27 Oct | Almere Buiten 16:40 | 0 min | — |
| Mon 26 Oct | Almere Buiten 16:41 | No data | — |
| Sun 25 Oct | Amsterdam Zuid 16:14 | No data | — |
| Sat 24 Oct | Almere Buiten 17:18 | +21 min | +21 min |
| Fri 23 Oct | Almere Buiten 16:39 | No data | — |
| Thu 22 Oct | Almere Buiten 16:45 | No data | — |
| Wed 21 Oct | Amsterdam Zuid 17:09 | No data | — |
| Tue 20 Oct | Schiphol Airport 16:12 | 0 min | — |
| Mon 19 Oct | Almere Buiten 16:40 | 0 min | — |
| Sun 18 Oct | Amsterdam Zuid 16:25 | +11 min | +11 min |
| Sat 17 Oct | Amsterdam Zuid 16:15 | No data | — |
| Fri 16 Oct | Almere Buiten 16:41 | No data | — |
| Thu 15 Oct | Rotterdam Centraal 15:35 | No data | — |