Train NS 2275 Amsterdam Centraal – Vlissingen

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:36 from Amsterdam Centraal · Thu 5 Nov

Next departure 21:36 today · Amsterdam Centraal
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 23 full · 2 partial · 3 no data
On-time · 90 days
93%
39/42 runs under 3 min
RT coverage: 39 full · 3 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sun 30 Aug Max en route +47 min · last fix heading to Vlissingen Souburg +44 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 10% · 4
  • On time 83% · 35
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 75% W n=4
  • 100% T n=4
  • 100% F n=3
  • 90% S n=10
  • 89% S n=9

Stops and timetable

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

Last 90 days, 42 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
21:36on time on time
21:41≈ on time ≈ on time
21:51 / 21:53≈ on time ≈ on time
21:58≈ on time ≈ on time
22:13 / 22:16≈ on time ≈ +1 min
22:24 / 22:25≈ on time ≈ +1 min
22:28 / 22:29≈ on time ≈ +1 min
22:36≈ on time ≈ on time
22:44≈ on time ≈ on time
22:48 / 22:51≈ on time ≈ on time
22:54≈ on time ≈ on time
23:06 / 23:07≈ on time ≈ +1 min
23:30 / 23:36≈ on time ≈ +1 min
23:45≈ on time ≈ +1 min
23:55≈ on time ≈ +1 min
00:00≈ on time ≈ +1 min
00:05≈ on time ≈ +1 min
00:11≈ on time ≈ +1 min
00:16≈ on time ≈ +1 min
00:26≈ on time ≈ +1 min
00:31≈ on time ≈ +1 min
00:36≈ on time ≈ +1 min
00:40on 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

DateLast stopFinalMax
Wed 4 Nov— 00:540 min+4 min
Tue 3 Nov— 00:420 min—
Mon 2 Nov— 22:490 min—
Sun 1 NovVlissingen Souburg 00:49Partial coverage0 min—
Sat 31 OctSchiedam Centrum 01:050 min—
Thu 29 Oct— 00:410 min—
Wed 28 Oct— 00:410 min—
Tue 27 Oct— 00:420 min—
Mon 26 Oct— 23:07No data—
Sun 25 OctVlissingen Souburg 00:57No data—
Sat 24 OctDelft 00:410 min—
Fri 23 Oct— 00:430 min—
Thu 22 Oct— 00:480 min—
Wed 21 Oct— 00:41No data—
Tue 20 Oct— 00:430 min—
Mon 19 Oct— 00:410 min—
Sun 18 OctVlissingen Souburg 00:50Partial coverage0 min—
Sat 17 OctVlissingen Souburg 00:520 min—
Fri 16 Oct— 00:410 min—
Thu 15 Oct— 00:430 min—
Wed 14 Oct— 00:410 min—
Tue 13 Oct— 00:410 min—
Mon 12 Oct— 00:42+1 min—
Sun 11 OctVlissingen Souburg 00:500 min—
Sat 10 OctSchiphol Airport 22:42+4 min+4 min
Fri 9 Oct— 00:410 min—
Thu 8 Oct— 01:260 min+24 min
Wed 7 Oct— 00:48+4 min+4 min
Tue 6 Oct— 00:460 min—
Mon 5 OctSchiedam Centrum 00:42Partial coverage0 min—