Train NS 2341 Amsterdam Centraal – Vlissingen

Amsterdam Centraal 13:06 → Vlissingen 15:50 Daily 2 h 44 min · 17 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dordrecht at 14:51 No data

  1. Amsterdam Centraal13:06
  2. Heemstede-Aerdenhout13:28
  3. Den Haag Laan v NOI13:53
  4. Schiedam Centrum14:14
  5. Dordrecht14:36
  6. Roosendaal15:00
  7. Vlissingen15:50

Next service: tomorrow 13:06 from Amsterdam Centraal · Sun 18 Oct

Next departure 13:06 tomorrow · Amsterdam Centraal
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 20 full · 2 partial · 8 no data
On-time · 90 days
92%
55/60 runs under 3 min
RT coverage: 58 full · 2 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 8 Oct Max en route +26 min · last fix heading to Middelburg +25 min
  • Tue 6 Oct Max en route +8 min · last fix heading to Middelburg +6 min
  • Fri 21 Aug Max en route +20 min · last fix heading to Rotterdam Blaak +6 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Dordrecht +4 min
  • Wed 16 Sept Max en route +4 min · last fix heading to Middelburg +4 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 88% · 53
  • 3–10 min 7% · 4
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 91% T n=11
  • 83% W n=6
  • 89% T n=9
  • 91% F n=11
  • 67% S n=3
  • 100% S n=8

Stops and timetable

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

StopSched.
13:06
13:11
13:21 / 13:23
13:28
13:43 / 13:45
13:53 / 13:55
13:58 / 14:00
14:06
14:14
14:19 / 14:21
14:24
14:36 / 14:37
15:00 / 15:02
15:12
15:31
15:43
15:50

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.

Recent runs

DateLast stopFinalMax
Sat 17 OctDordrecht 14:51No data—
Fri 16 OctMiddelburg 15:58Partial coverage0 min—
Thu 15 OctMiddelburg 15:58No data—
Wed 14 OctMiddelburg 16:29No data—
Tue 13 OctMiddelburg 15:58No data—
Mon 12 OctMiddelburg 15:570 min—
Sun 11 OctDordrecht 14:51+2 min+2 min
Sat 10 OctDordrecht 14:53+4 min+5 min
Fri 9 OctMiddelburg 15:57Partial coverage0 min—
Thu 8 OctMiddelburg 16:38+25 min+26 min
Wed 7 OctMiddelburg 15:58+1 min+3 min
Tue 6 OctMiddelburg 16:06+6 min+8 min
Mon 5 OctMiddelburg 15:590 min—
Sun 4 OctDordrecht 14:51No data—
Sat 3 OctDordrecht 14:54No data—
Fri 2 OctRotterdam Blaak 23:130 min+1 min
Thu 1 OctRotterdam Blaak 21:47−3 min+1 min
Wed 30 SeptRotterdam Blaak 19:590 min—
Tue 29 SeptRotterdam Blaak 19:590 min—
Mon 28 SeptRotterdam Blaak 23:440 min—
Sun 27 SeptRotterdam Blaak 00:120 min—
Sat 26 SeptDordrecht 14:54No data—
Fri 25 SeptRotterdam Blaak 22:46+2 min+18 min
Thu 24 SeptRotterdam Blaak 18:250 min+6 min
Wed 23 SeptRotterdam Blaak 17:040 min—
Tue 22 SeptRotterdam Blaak 18:230 min+1 min
Mon 21 SeptRotterdam Blaak 22:430 min+2 min
Sun 20 SeptRotterdam Blaak 16:050 min+6 min
Sat 19 SeptDordrecht 14:51No data—
Fri 18 SeptRotterdam Blaak 19:300 min—