Train NS 2329 Amsterdam Centraal – Vlissingen
It has not run yet today
Last recorded run: Tuesday 10 November 0 min
Next service: today 10:06 from Amsterdam Centraal · Wed 11 Nov
Last 30 days
Arrival delay at Vlissingen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 6 Oct Max en route +5 min · last fix heading to Middelburg +4 min
- Wed 16 Sept Max en route +4 min · last fix heading to Dordrecht +4 min
- Sun 20 Sept Max en route +3 min · last fix heading to Rotterdam Blaak +3 min
Distribution · 90 days
68 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 1% · 1
- On time 94% · 64
- 3–10 min 4% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=11
- 90% T n=10
- 89% W n=9
- 100% T n=9
- 100% F n=9
- 100% S n=11
- 89% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (17 stops).
Last 90 days, 68 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 |
|---|---|---|---|
| 10:06 | on time | on time | |
| 10:11 | ≈ on time | ≈ on time | |
| 10:21 / 10:23 | ≈ on time | ≈ on time | |
| 10:28 | ≈ on time | ≈ on time | |
| 10:43 / 10:45 | ≈ on time | ≈ +1 min | |
| 10:53 / 10:55 | ≈ on time | ≈ +1 min | |
| 10:58 / 10:59 | ≈ on time | ≈ +1 min | |
| 11:06 | ≈ on time | ≈ +1 min | |
| 11:14 | ≈ on time | ≈ +1 min | |
| 11:18 / 11:21 | ≈ on time | ≈ +1 min | |
| 11:24 | ≈ on time | ≈ +1 min | |
| 11:36 / 11:37 | ≈ on time | ≈ +1 min | |
| 12:00 / 12:02 | ≈ on time | ≈ +1 min | |
| 12:12 | ≈ on time | ≈ +1 min | |
| 12:31 | ≈ on time | ≈ +1 min | |
| 12:43 | ≈ on time | ≈ +1 min | |
| 12:50 | 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 |
|---|---|---|---|
| Tue 10 Nov | Middelburg 12:57Partial coverage | 0 min | — |
| Mon 9 Nov | Middelburg 12:58Partial coverage | 0 min | — |
| Sun 8 Nov | Delft 11:19 | 0 min | — |
| Sat 7 Nov | Delft 11:19 | 0 min | — |
| Fri 6 Nov | Middelburg 12:57 | No data | — |
| Thu 5 Nov | Middelburg 13:02 | No data | — |
| Wed 4 Nov | Middelburg 12:57Partial coverage | 0 min | — |
| Tue 3 Nov | Middelburg 12:58 | No data | — |
| Mon 2 Nov | Middelburg 12:58 | No data | — |
| Sun 1 Nov | Dordrecht 11:52 | 0 min | — |
| Sat 31 Oct | Dordrecht 11:51 | 0 min | — |
| Fri 30 Oct | Middelburg 12:58 | No data | — |
| Thu 29 Oct | Middelburg 12:59Partial coverage | 0 min | — |
| Wed 28 Oct | Middelburg 13:00Partial coverage | 0 min | — |
| Tue 27 Oct | Middelburg 12:57Partial coverage | 0 min | — |
| Mon 26 Oct | Middelburg 12:59 | No data | — |
| Sun 25 Oct | Vlissingen Souburg 13:21 | No data | — |
| Sat 24 Oct | Vlissingen Souburg 13:20 | 0 min | — |
| Fri 23 Oct | Middelburg 13:00 | No data | — |
| Thu 22 Oct | Middelburg 13:10 | No data | — |
| Wed 21 Oct | Middelburg 13:09 | No data | — |
| Tue 20 Oct | Middelburg 12:57 | 0 min | — |
| Mon 19 Oct | Middelburg 12:58Partial coverage | 0 min | — |
| Sun 18 Oct | Dordrecht 12:01 | 0 min | — |
| Sat 17 Oct | Dordrecht 12:04 | 0 min | — |
| Fri 16 Oct | Middelburg 12:57 | 0 min | — |
| Thu 15 Oct | Middelburg 12:57 | 0 min | — |
| Wed 14 Oct | Middelburg 12:58 | 0 min | — |
| Tue 13 Oct | Middelburg 12:58 | No data | — |
| Mon 12 Oct | Middelburg 12:59 | 0 min | — |