Train NS 2346 Vlissingen – Amsterdam Centraal

Vlissingen 13:40 → Amsterdam Centraal 16:25 Daily 2 h 45 min · 17 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 16:40 0 min

  1. Vlissingen13:40
  2. Bergen op Zoom14:18
  3. Dordrecht14:53
  4. Schiedam Centrum15:16
  5. Den Haag Laan v NOI15:35
  6. Amsterdam Sloterdijk16:19
  7. Amsterdam Centraal16:25

Next service: tomorrow 13:40 from Vlissingen · Fri 30 Oct

Full trip card
Next departure 13:40 tomorrow · Vlissingen
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 15 full · 9 partial · 6 no data
On-time · 90 days
98%
53/54 runs under 3 min
RT coverage: 45 full · 9 partial · 35 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: +1 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

  • Tue 6 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

StopSched.
Vlissingen
13:40
Middelburg
13:46
Goes
13:57 / 13:58
Bergen op Zoom
14:18 / 14:19
Roosendaal
14:28 / 14:31
Dordrecht
14:53 / 14:54
Rotterdam Blaak
15:05
Rotterdam Centraal
15:08 / 15:11
Schiedam Centrum
15:16
Delft
15:24
Den Haag HS
15:31 / 15:32
Den Haag Laan v NOI
15:35 / 15:36
Leiden Centraal
15:45 / 15:47
Heemstede-Aerdenhout
16:01
Haarlem
16:06 / 16:10
Amsterdam Sloterdijk
16:19
Amsterdam Centraal
16:25

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
Thu 29 OctAmsterdam Sloterdijk 16:40Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 16:330 min—
Tue 27 OctAmsterdam Sloterdijk 16:34Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 16:34Partial coverage0 min—
Sun 25 OctAmsterdam Sloterdijk 16:34No data—
Sat 24 OctAmsterdam Sloterdijk 16:34+1 min—
Fri 23 OctAmsterdam Sloterdijk 16:350 min—
Thu 22 OctAmsterdam Sloterdijk 16:34No data—
Wed 21 OctAmsterdam Sloterdijk 16:33No data—
Tue 20 OctAmsterdam Sloterdijk 16:360 min—
Mon 19 OctAmsterdam Sloterdijk 16:35Partial coverage0 min—
Sun 18 OctAmsterdam Sloterdijk 16:34+1 min+1 min
Sat 17 OctAmsterdam Sloterdijk 16:340 min—
Fri 16 OctAmsterdam Sloterdijk 16:340 min—
Thu 15 OctAmsterdam Sloterdijk 16:34Partial coverage0 min—
Wed 14 OctHeemstede-Aerdenhout 16:16No data—
Tue 13 OctAmsterdam Sloterdijk 16:34No data—
Mon 12 OctAmsterdam Sloterdijk 16:34Partial coverage0 min—
Sun 11 OctAmsterdam Sloterdijk 16:370 min—
Sat 10 OctAmsterdam Sloterdijk 16:330 min—
Fri 9 OctAmsterdam Sloterdijk 16:34+1 min—
Thu 8 OctAmsterdam Sloterdijk 16:34Partial coverage+1 min—
Wed 7 OctAmsterdam Sloterdijk 16:34Partial coverage0 min+3 min
Tue 6 OctAmsterdam Sloterdijk 16:37Partial coverage+3 min+3 min
Mon 5 OctAmsterdam Sloterdijk 16:35+1 min—
Sun 4 OctDordrecht 23:53−1 min+4 min
Sat 3 OctDordrecht 00:160 min—
Fri 2 OctDordrecht 00:140 min—
Thu 1 OctAmsterdam Sloterdijk 16:34No data—
Wed 30 SeptDordrecht 19:45−1 min—