Train NS 2267 Amsterdam Centraal – Vlissingen

Amsterdam Centraal 19:36 → Vlissingen 22:39 Daily 3 h 03 min · 23 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 19:36 from Amsterdam Centraal · Fri 6 Nov

Next departure 19:36 today · Amsterdam Centraal
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 23 full · 0 partial · 5 no data
On-time · 90 days
87%
41/47 runs under 3 min
RT coverage: 47 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Mon 10 Aug Max en route +11 min · last fix heading to Amsterdam Sloterdijk +11 min
  • Sat 29 Aug Max en route +9 min · last fix heading to Amsterdam Sloterdijk +9 min
  • Sun 16 Aug Max en route +5 min · last fix heading to Vlissingen Souburg +5 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Kruiningen-Yerseke +4 min

Distribution · 90 days

47 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 21% · 10
  • On time 66% · 31
  • 3–10 min 11% · 5
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 100% T n=6
  • 100% W n=4
  • 100% T n=6
  • 80% F n=5
  • 78% S n=9
  • 75% S n=8

Stops and timetable

Timetable of the latest run from the operator’s GTFS (23 stops).

Last 90 days, 47 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.

StopSched.Usually 9 days in 10
19:36on time on time
19:41≈ on time ≈ on time
19:51 / 19:53≈ on time ≈ on time
19:58≈ on time ≈ on time
20:13 / 20:16≈ on time ≈ +1 min
20:24 / 20:25≈ on time ≈ +1 min
20:28 / 20:29≈ on time ≈ +1 min
20:36≈ on time ≈ +1 min
20:44≈ on time ≈ +1 min
20:48 / 20:51≈ on time ≈ +2 min
20:54≈ on time ≈ +2 min
21:06 / 21:07≈ on time ≈ +2 min
21:30 / 21:36≈ on time ≈ +2 min
21:45≈ on time ≈ +3 min
21:55≈ on time ≈ +3 min
22:00≈ on time ≈ +3 min
22:05≈ on time ≈ +3 min
22:11≈ on time ≈ +3 min
22:16≈ on time ≈ +3 min
22:26≈ on time ≈ +3 min
22:31≈ on time ≈ +3 min
22:36≈ on time ≈ +4 min
22:39on 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

DateLast stopFinalMax
Thu 5 Nov— 22:440 min—
Wed 4 Nov— 22:390 min—
Tue 3 Nov— 22:390 min—
Mon 2 Nov— 22:44+2 min+3 min
Sun 1 NovVlissingen Souburg 22:490 min—
Sat 31 OctVlissingen Souburg 22:500 min—
Thu 29 Oct— 22:43+2 min+2 min
Wed 28 Oct— 22:410 min—
Tue 27 Oct— 22:430 min—
Mon 26 OctHaarlem 22:40No data—
Sun 25 OctVlissingen Souburg 23:00No data—
Sat 24 OctMiddelburg 23:040 min—
Fri 23 Oct— 22:43+2 min+2 min
Thu 22 Oct— 22:430 min—
Wed 21 Oct— 22:40No data—
Tue 20 Oct— 21:330 min—
Mon 19 Oct— 22:470 min—
Sun 18 OctVlissingen Souburg 22:50+1 min+1 min
Sat 17 OctVlissingen Souburg 22:50No data—
Fri 16 OctHaarlem 22:43+2 min+2 min
Thu 15 Oct— 22:410 min—
Wed 14 OctAmsterdam Sloterdijk 22:41No data—
Tue 13 Oct— 22:410 min—
Mon 12 Oct— 22:410 min—
Sun 11 OctVlissingen Souburg 22:52+3 min+3 min
Sat 10 OctKruiningen-Yerseke 22:19+4 min+4 min
Fri 9 Oct— 22:48+5 min+5 min
Thu 8 Oct— 22:43+2 min+2 min
Wed 7 Oct— 22:400 min—
Tue 6 Oct— 22:400 min—