Train NS Int 9535 Brussel-Zuid – Lelystad Centrum
✓ Today’s run finished
Today, last fix heading to Almere Buiten at 12:39 No data
- Brussel-Zuid09:49
- Antwerpen-Centraal10:23
- Rotterdam Centraal11:17
- Amsterdam Zuid11:54
- Almere Centrum12:17
- Almere Buiten12:25
- Lelystad Centrum12:36
Next service: tomorrow 09: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
- Thu 8 Oct Max en route +13 min · last fix heading to Almere Buiten +12 min
- Sun 18 Oct Max en route +5 min · last fix heading to Rotterdam Centraal +5 min
- Sun 11 Oct Max en route +4 min · last fix heading to Amsterdam Zuid +4 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 84% · 16
- 3–10 min 11% · 2
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=4
- 100% W n=3
- 50% T n=2
- 100% F n=1
- 100% S n=3
- 33% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 09:49 | on time | on time | |
| 10:23 / 10:35 | ≈ on time | ≈ +1 min | |
| 11:17 / 11:21 | ≈ on time | ≈ +2 min | |
| 11:47 / 11:48 | ≈ on time | ≈ +3 min | |
| 11:54 / 11:56 | ≈ on time | ≈ +3 min | |
| 12:17 / 12:20 | ≈ on time | ≈ +4 min | |
| 12:25 | ≈ on time | ≈ +4 min | |
| 12:36 | on time | +4 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 12:39 | No data | — |
| Thu 5 Nov | Almere Buiten 12:39 | No data | — |
| Wed 4 Nov | Almere Buiten 12:39Partial coverage | +1 min | +1 min |
| Tue 3 Nov | Almere Buiten 13:04Partial coverage | 0 min | — |
| Mon 2 Nov | Almere Buiten 12:39Partial coverage | 0 min | — |
| Sun 1 Nov | Amsterdam Zuid 12:15 | 0 min | — |
| Sat 31 Oct | Almere Buiten 12:40 | +1 min | +2 min |
| Fri 30 Oct | Almere Buiten 12:39 | No data | — |
| Thu 29 Oct | Almere Buiten 12:40 | 0 min | — |
| Wed 28 Oct | Almere Buiten 13:20 | 0 min | — |
| Tue 27 Oct | Almere Buiten 12:56 | No data | — |
| Mon 26 Oct | Almere Buiten 13:00 | No data | — |
| Sun 25 Oct | Schiphol Airport 13:08 | No data | — |
| Sat 24 Oct | Almere Buiten 12:40 | 0 min | +2 min |
| Fri 23 Oct | Almere Buiten 13:00 | No data | — |
| Thu 22 Oct | Almere Buiten 13:20 | No data | — |
| Wed 21 Oct | — 11:29 | No data | — |
| Tue 20 Oct | Almere Buiten 12:40 | 0 min | — |
| Mon 19 Oct | Almere Buiten 12:57 | 0 min | — |
| Sun 18 Oct | Rotterdam Centraal 12:30 | +5 min | +5 min |
| Sat 17 Oct | Amsterdam Zuid 12:15 | No data | — |
| Fri 16 Oct | Almere Buiten 12:41 | No data | — |
| Thu 15 Oct | Almere Buiten 12:41 | No data | — |
| Wed 14 Oct | Almere Buiten 12:41 | No data | — |
| Tue 13 Oct | Almere Buiten 12:45 | 0 min | — |
| Sun 11 Oct | Amsterdam Zuid 12:17 | +4 min | +4 min |
| Sat 10 Oct | Almere Buiten 12:39 | 0 min | — |
| Fri 9 Oct | Rotterdam Centraal 12:38 | 0 min | — |
| Thu 8 Oct | Almere Buiten 13:02Partial coverage | +12 min | +13 min |
| Wed 7 Oct | Almere Buiten 12:39Partial coverage | 0 min | — |