Train NS 2260 Vlissingen – Amsterdam Centraal

Vlissingen 16:51 → Amsterdam Centraal 19:55 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 16:51 from Vlissingen · Thu 5 Nov

Next departure 16:51 today · Vlissingen
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 38 full · 1 partial · 42 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: +3 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

  • Fri 9 Oct Max en route +15 min · last fix heading to Rotterdam Blaak +15 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Roosendaal +5 min

Distribution · 90 days

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

  • Early 28% · 11
  • On time 67% · 26
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
16:51on time on time
16:55≈ on time ≈ +1 min
16:59≈ on time ≈ +1 min
17:04≈ on time ≈ +1 min
17:13 / 17:14≈ on time ≈ +1 min
17:19≈ on time ≈ +2 min
17:24≈ on time ≈ +2 min
17:30≈ on time ≈ +2 min
17:34≈ on time ≈ +2 min
17:44 / 17:45≈ on time ≈ +2 min
17:54 / 17:59≈ on time ≈ +2 min
18:23 / 18:24≈ on time ≈ +2 min
18:35≈ on time ≈ +2 min
18:38 / 18:41≈ on time ≈ +2 min
18:46≈ on time ≈ +2 min
18:54≈ on time ≈ +2 min
19:01 / 19:02≈ on time ≈ +2 min
19:05 / 19:06≈ on time ≈ +2 min
19:15 / 19:17≈ on time ≈ +2 min
19:31≈ on time ≈ +1 min
19:36 / 19:40≈ on time ≈ +1 min
19:49≈ on time ≈ +1 min
19:55on 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 NovRoosendaal 19:57Partial coverage0 min+1 min
Tue 3 NovRoosendaal 19:540 min—
Mon 2 NovRoosendaal 19:57No data—
Sun 1 NovAmsterdam Sloterdijk 20:030 min—
Sat 31 OctAmsterdam Sloterdijk 20:06+3 min+3 min
Fri 30 OctDelft 19:08No data—
Thu 29 OctRoosendaal 19:500 min+13 min
Wed 28 OctRoosendaal 19:570 min—
Tue 27 OctRoosendaal 20:01No data—
Mon 26 OctRoosendaal 18:38+5 min+5 min
Sun 25 OctAmsterdam Sloterdijk 20:04No data—
Sat 24 OctAmsterdam Sloterdijk 20:040 min—
Fri 23 OctLeiden Centraal 20:01+1 min+2 min
Thu 22 OctRotterdam Blaak 20:190 min—
Wed 21 OctRotterdam Blaak 20:01No data—
Tue 20 OctSchiedam Centrum 18:500 min—
Mon 19 OctRotterdam Blaak 19:57No data—
Sun 18 OctAmsterdam Sloterdijk 20:040 min+1 min
Sat 17 OctAmsterdam Sloterdijk 20:04No data—
Fri 16 OctAmsterdam Sloterdijk 20:03No data—
Thu 15 OctDordrecht 19:58No data—
Wed 14 OctHaarlem 19:57No data—
Tue 13 OctRotterdam Blaak 19:570 min—
Mon 12 OctRotterdam Blaak 20:170 min—
Sun 11 OctAmsterdam Sloterdijk 20:020 min—
Sat 10 OctAmsterdam Sloterdijk 20:030 min—
Fri 9 OctRotterdam Blaak 20:08+15 min+15 min
Thu 8 OctRoosendaal 19:560 min+1 min
Wed 7 OctRoosendaal 19:560 min—
Tue 6 OctRoosendaal 19:560 min—