Train NS 2366 Vlissingen – Amsterdam Centraal
It has not run yet today
Last recorded run: Wednesday 11 November 0 min
Next service: today 18:40 from Vlissingen · Thu 12 Nov
Last 30 days
Arrival delay at Amsterdam Centraal, 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 23 Oct Max en route +10 min · last fix heading to Bergen op Zoom +8 min
- Thu 8 Oct Max en route +6 min · last fix heading to — +6 min
Distribution · 90 days
33 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 31
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=5
- 67% T n=3
- 80% F n=5
- 100% S n=6
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (17 stops).
Last 90 days, 33 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 |
|---|---|---|---|
| 18:40 | on time | on time | |
| 18:46 | ≈ on time | ≈ on time | |
| 18:57 / 18:58 | ≈ on time | ≈ on time | |
| 19:18 / 19:19 | ≈ on time | ≈ on time | |
| 19:28 / 19:31 | ≈ on time | ≈ on time | |
| 19:53 / 19:54 | ≈ on time | ≈ +1 min | |
| 20:05 | ≈ on time | ≈ +1 min | |
| 20:08 / 20:11 | ≈ on time | ≈ +1 min | |
| 20:16 | ≈ on time | ≈ +1 min | |
| 20:24 | ≈ on time | ≈ +1 min | |
| 20:31 / 20:32 | ≈ on time | ≈ +1 min | |
| 20:35 / 20:36 | ≈ on time | ≈ +1 min | |
| 20:45 / 20:47 | ≈ on time | ≈ +1 min | |
| 21:01 | ≈ on time | ≈ +1 min | |
| 21:06 / 21:10 | ≈ on time | ≈ +1 min | |
| 21:19 | ≈ on time | ≈ +1 min | |
| 21:25 | 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 |
|---|---|---|---|
| Wed 11 Nov | — 21:24 | 0 min | — |
| Tue 10 Nov | — 21:29 | +1 min | +2 min |
| Mon 9 Nov | — 21:27 | +1 min | — |
| Sun 8 Nov | Amsterdam Sloterdijk 21:34 | +1 min | — |
| Sat 7 Nov | Amsterdam Sloterdijk 21:34 | 0 min | — |
| Fri 6 Nov | Vlissingen 21:24 | +1 min | — |
| Thu 5 Nov | — 21:27 | 0 min | — |
| Wed 4 Nov | — 21:29 | +2 min | +3 min |
| Mon 2 Nov | — 21:27 | +1 min | +2 min |
| Sun 1 Nov | Amsterdam Sloterdijk 21:34 | +1 min | — |
| Sat 31 Oct | Amsterdam Sloterdijk 21:34 | 0 min | — |
| Fri 30 Oct | Middelburg 19:00 | 0 min | — |
| Thu 29 Oct | — 19:03 | 0 min | — |
| Wed 28 Oct | — 21:27 | 0 min | — |
| Tue 27 Oct | — 19:30 | 0 min | — |
| Mon 26 Oct | Roosendaal 21:47 | No data | — |
| Sun 25 Oct | Amsterdam Sloterdijk 21:48 | No data | — |
| Sat 24 Oct | Amsterdam Sloterdijk 21:34 | 0 min | — |
| Fri 23 Oct | Bergen op Zoom 21:41 | +8 min | +10 min |
| Thu 22 Oct | Vlissingen 21:27 | No data | — |
| Wed 21 Oct | Vlissingen 21:26 | 0 min | — |
| Tue 20 Oct | Middelburg 21:17 | 0 min | — |
| Mon 19 Oct | Vlissingen 21:26Partial coverage | 0 min | — |
| Sun 18 Oct | Amsterdam Sloterdijk 21:34 | +1 min | +1 min |
| Sat 17 Oct | Amsterdam Sloterdijk 21:34 | 0 min | — |
| Fri 16 Oct | Dordrecht 21:26 | 0 min | — |
| Thu 15 Oct | — 21:27 | No data | — |
| Wed 14 Oct | Roosendaal 21:33 | No data | — |
| Tue 13 Oct | Vlissingen 19:36 | No data | — |
| Mon 12 Oct | Vlissingen 21:27Partial coverage | 0 min | — |