Train NS 2313 Amsterdam Centraal – Vlissingen

Amsterdam Centraal 06:06 → Vlissingen 08:50 Mon, Tue, Wed, Thu, Fri 2 h 44 min · 17 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Middelburg at 08:58 No data

  1. Amsterdam Centraal06:06
  2. Heemstede-Aerdenhout06:28
  3. Den Haag Laan v NOI06:53
  4. Schiedam Centrum07:14
  5. Dordrecht07:36
  6. Middelburg08:43
  7. Vlissingen08:50

Next service: Monday 06:06 from Amsterdam Centraal · Mon 9 Nov

Next departure 06:06 Monday · Amsterdam Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 14 full · 6 partial · 3 no data
On-time · 90 days
98%
55/56 runs under 3 min
RT coverage: 49 full · 7 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Tue 6 Oct Max en route +15 min · last fix heading to Middelburg +14 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=11
  • 91% T n=11
  • 100% W n=11
  • 100% T n=12
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 56 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
06:06on time on time
06:11≈ on time ≈ on time
06:21 / 06:23≈ on time ≈ on time
06:28≈ on time ≈ on time
06:43 / 06:45≈ on time ≈ on time
06:53 / 06:55≈ on time ≈ on time
06:58 / 06:59≈ on time ≈ on time
07:06≈ on time ≈ on time
07:14≈ on time ≈ on time
07:18 / 07:21≈ on time ≈ on time
07:24≈ on time ≈ on time
07:36 / 07:37≈ on time ≈ on time
08:00 / 08:02≈ on time ≈ on time
08:12≈ on time ≈ on time
08:31≈ on time ≈ on time
08:43≈ on time ≈ on time
08:50on time on time

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
Fri 6 NovMiddelburg 08:58No data—
Thu 5 NovMiddelburg 09:03Partial coverage0 min—
Wed 4 NovMiddelburg 08:580 min+1 min
Tue 3 NovMiddelburg 08:58Partial coverage0 min—
Mon 2 NovMiddelburg 08:57No data—
Fri 30 OctMiddelburg 08:580 min—
Thu 29 OctMiddelburg 08:57Partial coverage0 min—
Wed 28 OctMiddelburg 08:580 min—
Tue 27 OctMiddelburg 09:00Partial coverage0 min—
Mon 26 OctMiddelburg 08:59Partial coverage0 min—
Sun 25 OctSchiedam Centrum 07:29No data—
Fri 23 OctMiddelburg 09:370 min—
Thu 22 OctMiddelburg 08:580 min—
Wed 21 OctMiddelburg 08:570 min—
Tue 20 OctMiddelburg 08:570 min—
Mon 19 OctMiddelburg 08:58Partial coverage0 min—
Fri 16 OctMiddelburg 08:580 min—
Thu 15 OctMiddelburg 09:060 min+1 min
Wed 14 OctMiddelburg 08:580 min—
Tue 13 OctMiddelburg 08:580 min—
Mon 12 OctMiddelburg 08:590 min—
Fri 9 OctMiddelburg 08:580 min—
Thu 8 OctMiddelburg 08:580 min—
Wed 7 OctMiddelburg 08:570 min—
Tue 6 OctMiddelburg 09:19Partial coverage+14 min+15 min
Mon 5 OctRotterdam Blaak 12:20+2 min+2 min
Fri 2 OctRotterdam Blaak 18:440 min+6 min
Thu 1 OctRotterdam Blaak 19:190 min+6 min
Wed 30 SeptRotterdam Blaak 22:42−1 min+5 min
Tue 29 SeptRotterdam Blaak 20:47−3 min+1 min