Train NS 2219 Amsterdam Centraal – Vlissingen

Amsterdam Centraal 07:36 → Vlissingen 10: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 07:36 from Amsterdam Centraal · Fri 6 Nov

Next departure 07:36 today · Amsterdam Centraal
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 23 full · 2 partial · 4 no data
On-time · 90 days
100%
57/57 runs under 3 min
RT coverage: 55 full · 2 partial · 31 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: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 57
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=8
  • 100% T n=9
  • 100% F n=9
  • 100% S n=7
  • 100% S n=5

Stops and timetable

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

Last 90 days, 57 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
07:36on time on time
07:41≈ on time ≈ on time
07:51 / 07:53≈ on time ≈ on time
07:58≈ on time ≈ on time
08:13 / 08:15≈ on time ≈ on time
08:23 / 08:25≈ on time ≈ on time
08:28 / 08:29≈ on time ≈ on time
08:36≈ on time ≈ on time
08:44≈ on time ≈ on time
08:48 / 08:51≈ on time ≈ on time
08:54≈ on time ≈ on time
09:06 / 09:07≈ on time ≈ on time
09:30 / 09:36≈ on time ≈ +1 min
09:45≈ on time ≈ +1 min
09:55≈ on time ≈ +1 min
10:00≈ on time ≈ +1 min
10:05≈ on time ≈ +1 min
10:11≈ on time ≈ +1 min
10:16≈ on time ≈ +1 min
10:26≈ on time ≈ +1 min
10:31≈ on time ≈ +1 min
10:36≈ on time ≈ +1 min
10:39on 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
Thu 5 NovVlissingen Souburg 10:54Partial coverage0 min—
Wed 4 NovVlissingen Souburg 10:490 min—
Tue 3 NovVlissingen Souburg 10:540 min—
Mon 2 NovVlissingen Souburg 10:54No data—
Sun 1 NovVlissingen Souburg 10:52+1 min+3 min
Sat 31 OctVlissingen Souburg 10:50+1 min+3 min
Fri 30 OctVlissingen Souburg 10:500 min—
Thu 29 OctVlissingen Souburg 10:510 min—
Wed 28 OctVlissingen Souburg 10:500 min—
Tue 27 OctVlissingen Souburg 10:530 min—
Mon 26 OctVlissingen Souburg 10:500 min—
Sun 25 OctVlissingen Souburg 10:50No data—
Sat 24 OctVlissingen Souburg 10:53+3 min+4 min
Fri 23 OctVlissingen Souburg 10:500 min—
Thu 22 OctVlissingen Souburg 10:500 min—
Wed 21 OctVlissingen Souburg 10:50No data—
Tue 20 OctVlissingen Souburg 10:540 min—
Mon 19 OctVlissingen Souburg 10:500 min—
Sun 18 OctVlissingen Souburg 10:52+2 min+4 min
Sat 17 OctVlissingen Souburg 10:500 min—
Fri 16 OctVlissingen Souburg 10:500 min—
Thu 15 OctRoosendaal 10:580 min—
Wed 14 OctVlissingen Souburg 10:50No data—
Tue 13 OctVlissingen Souburg 10:500 min—
Mon 12 OctVlissingen Souburg 10:500 min—
Sun 11 OctVlissingen Souburg 10:50+1 min+2 min
Sat 10 OctVlissingen Souburg 10:50+2 min+2 min
Fri 9 OctVlissingen Souburg 10:500 min+3 min
Thu 8 OctVlissingen Souburg 10:51Partial coverage+1 min+1 min
Wed 7 OctVlissingen Souburg 12:020 min—