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