Train NS 4315 Hoofddorp – Lelystad Centrum
✓ Today’s run finished
Today, last fix heading to Almere Oostvaarders at 06:38 No data
- Hoofddorp05:20
- Amsterdam Zuid05:36
- Duivendrecht05:43
- Almere Poort06:05
- Almere Centrum06:12
- Almere Oostvaarders06:22
- Lelystad Centrum06:33
Next service: Monday 05:20 from Hoofddorp · Mon 9 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
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 100% · 26
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 100% W n=5
- 100% T n=6
- 100% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 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 |
|---|---|---|---|
| 05:20 | on time | on time | |
| 05:25 / 05:31 | ≈ on time | ≈ on time | |
| 05:36 / 05:37 | ≈ on time | ≈ on time | |
| 05:40 | ≈ on time | ≈ on time | |
| 05:43 / 05:44 | ≈ on time | ≈ on time | |
| 05:46 | ≈ on time | ≈ on time | |
| 05:53 / 05:59 | ≈ on time | ≈ on time | |
| 06:05 | ≈ on time | ≈ +1 min | |
| 06:09 | ≈ on time | ≈ +1 min | |
| 06:12 / 06:13 | ≈ on time | ≈ +1 min | |
| 06:16 | ≈ on time | ≈ +1 min | |
| 06:19 | ≈ on time | ≈ +1 min | |
| 06:22 | ≈ on time | ≈ +1 min | |
| 06:33 | on time | +1 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 Oostvaarders 06:38 | No data | — |
| Thu 5 Nov | Almere Oostvaarders 06:37Partial coverage | 0 min | — |
| Wed 4 Nov | Almere Oostvaarders 06:39 | +2 min | +2 min |
| Tue 3 Nov | Almere Oostvaarders 06:37 | 0 min | — |
| Mon 2 Nov | Almere Oostvaarders 06:34 | 0 min | — |
| Fri 30 Oct | Almere Oostvaarders 06:37 | 0 min | — |
| Thu 29 Oct | Almere Oostvaarders 06:39 | 0 min | — |
| Wed 28 Oct | Almere Oostvaarders 06:39 | 0 min | — |
| Tue 27 Oct | Almere Oostvaarders 06:39 | 0 min | — |
| Mon 26 Oct | Almere Oostvaarders 06:40 | +1 min | — |
| Fri 23 Oct | Almere Oostvaarders 06:36 | 0 min | — |
| Thu 22 Oct | Almere Oostvaarders 06:39Partial coverage | +2 min | +3 min |
| Wed 21 Oct | Almere Oostvaarders 06:38 | +1 min | +1 min |
| Tue 20 Oct | Almere Oostvaarders 06:37 | 0 min | — |
| Mon 19 Oct | Almere Oostvaarders 06:37 | 0 min | — |
| Fri 16 Oct | Almere Oostvaarders 06:40 | 0 min | — |
| Thu 15 Oct | Almere Oostvaarders 06:40 | 0 min | — |
| Wed 14 Oct | Almere Oostvaarders 06:40 | +1 min | — |
| Tue 13 Oct | Almere Oostvaarders 06:39 | 0 min | — |
| Mon 12 Oct | Almere Oostvaarders 06:41 | +2 min | +2 min |
| Fri 9 Oct | Almere Oostvaarders 06:37 | 0 min | — |
| Thu 8 Oct | Almere Oostvaarders 06:37Partial coverage | 0 min | — |
| Wed 7 Oct | Almere Oostvaarders 06:38 | 0 min | +3 min |
| Tue 6 Oct | Almere Oostvaarders 06:36 | 0 min | — |
| Mon 5 Oct | Amsterdam RAI 12:09 | 0 min | — |
| Fri 2 Oct | Amsterdam RAI 18:39 | 0 min | +4 min |
| Thu 1 Oct | Amsterdam RAI 18:59 | 0 min | +2 min |
| Wed 30 Sept | Almere Oostvaarders 06:36 | No data | — |
| Tue 29 Sept | Almere Oostvaarders 06:38 | No data | — |
| Mon 28 Sept | Almere Oostvaarders 06:36 | No data | — |