Train NS 2280 Vlissingen – Amsterdam Centraal

Vlissingen 21:51 → Amsterdam Centraal 00:55 Daily 3 h 04 min · 23 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 21:51 from Vlissingen · Fri 6 Nov

Full trip card
Next departure 21:51 today · Vlissingen
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 1 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

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

  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 9% · 3
  • On time 88% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=4
  • 80% T n=5
  • 100% F n=3
  • 100% S n=4
  • 100% S n=8

Stops and timetable

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

Last 90 days, 34 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
Vlissingen
21:51on time on time
Vlissingen Souburg
21:55≈ on time ≈ on time
Middelburg
21:59≈ on time ≈ on time
Arnemuiden
22:04≈ on time ≈ on time
Goes
22:13 / 22:14≈ on time ≈ on time
Kapelle-Biezelinge
22:19≈ on time ≈ on time
Kruiningen-Yerseke
22:24≈ on time ≈ on time
Krabbendijke
22:30≈ on time ≈ on time
Rilland-Bath
22:34≈ on time ≈ on time
Bergen op Zoom
22:44 / 22:45≈ on time ≈ on time
Roosendaal
22:54 / 23:01≈ on time ≈ on time
Dordrecht
23:23 / 23:24≈ on time ≈ on time
Rotterdam Blaak
23:35≈ on time ≈ on time
Rotterdam Centraal
23:38 / 23:41≈ on time ≈ on time
Schiedam Centrum
23:46≈ on time ≈ on time
Delft
23:54≈ on time ≈ on time
Den Haag HS
00:01 / 00:02≈ on time ≈ on time
Den Haag Laan v NOI
00:05 / 00:06≈ on time ≈ on time
Leiden Centraal
00:15 / 00:17≈ on time ≈ on time
Heemstede-Aerdenhout
00:31≈ on time ≈ on time
Haarlem
00:36 / 00:40≈ on time ≈ on time
Amsterdam Sloterdijk
00:49≈ on time ≈ on time
Amsterdam Centraal
00:55on 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

DateLast stopFinalMax
Thu 5 Nov— 00:540 min—
Wed 4 Nov— 00:590 min—
Tue 3 Nov— 00:570 min—
Sun 1 NovDelft 00:120 min—
Sat 31 OctRoosendaal 23:150 min—
Thu 29 Oct— 00:56+1 min—
Wed 28 Oct— 00:210 min—
Tue 27 Oct— 00:570 min—
Mon 26 Oct— 00:560 min—
Sun 25 OctAmsterdam Sloterdijk 01:040 min—
Sat 24 OctKruiningen-Yerseke 00:560 min—
Fri 23 Oct— 00:570 min—
Thu 22 Oct— 00:560 min—
Wed 21 Oct— 22:55No data—
Tue 20 Oct— 01:010 min—
Mon 19 Oct— 00:560 min—
Sun 18 OctAmsterdam Sloterdijk 01:050 min—
Sat 17 OctAmsterdam Sloterdijk 01:030 min—
Fri 16 Oct— 00:570 min+1 min
Thu 15 Oct— 00:560 min—
Wed 14 Oct— 01:220 min—
Tue 13 Oct— 23:240 min—
Mon 12 Oct— 00:560 min—
Sun 11 OctAmsterdam Sloterdijk 01:040 min—
Sat 10 OctArnemuiden 23:400 min—
Fri 9 Oct— 00:570 min—
Thu 8 Oct— 01:03+4 min+4 min
Wed 7 Oct— 00:560 min—
Tue 6 Oct— 00:560 min—
Mon 5 OctDen Haag HS 00:560 min+6 min