Train NS 2333 Amsterdam Centraal – Vlissingen

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

Running now · updated 10:58

Heading to Vlissingen 0 min

Estimated arrival at Vlissingen 13:50

  1. Amsterdam Centraal11:06
  2. Heemstede-Aerdenhout11:28
  3. Den Haag Laan v NOI11:53
  4. Schiedam Centrum12:14
  5. Dordrecht12:36
  6. Bergen op Zoom13:12
  7. Vlissingen13:50

Today it is running no worse than usual: typical arrival delay is 0 min; 88% of the last 25 runs arrived on time.

On-time · 30 days
88%
22/25 runs under 3 min
RT coverage: 19 full · 6 partial · 5 no data
On-time · 90 days
94%
68/72 runs under 3 min
RT coverage: 66 full · 6 partial · 17 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: +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

Worst days

  • Sun 18 Oct Max en route +9 min · last fix heading to Dordrecht +9 min
  • Sat 5 Sept Max en route +7 min · last fix heading to Rotterdam Blaak +7 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Dordrecht +4 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Dordrecht +3 min

Distribution · 90 days

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

  • Early 4% · 3
  • On time 90% · 65
  • 3–10 min 6% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=10
  • 100% W n=9
  • 100% T n=10
  • 100% F n=11
  • 83% S n=12
  • 75% S n=8

Stops and timetable

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

StopSched.Today
11:06
11:11
11:21 / 11:23
11:28
11:43 / 11:45
11:53 / 11:55
11:58 / 11:59
12:06
12:14
12:18 / 12:21
12:24
12:36 / 12:37
13:00 / 13:02
13:12
13:31
13:43
13: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
Wed 28 OctAmsterdam Centraal 10:54Partial coverage0 min—
Tue 27 OctMiddelburg 13:57No data—
Mon 26 OctMiddelburg 13:58Partial coverage0 min—
Sun 25 OctVlissingen Souburg 14:21No data—
Sat 24 OctVlissingen Souburg 14:200 min—
Fri 23 OctMiddelburg 13:590 min—
Thu 22 OctMiddelburg 14:010 min—
Wed 21 OctMiddelburg 13:57No data—
Tue 20 OctMiddelburg 13:570 min—
Mon 19 OctMiddelburg 13:58Partial coverage0 min—
Sun 18 OctDordrecht 13:14+9 min+9 min
Sat 17 OctDordrecht 13:010 min—
Fri 16 OctMiddelburg 13:580 min—
Thu 15 OctMiddelburg 14:37No data—
Wed 14 OctMiddelburg 13:580 min—
Tue 13 OctMiddelburg 13:57No data—
Mon 12 OctMiddelburg 13:580 min—
Sun 11 OctDordrecht 12:51+4 min+4 min
Sat 10 OctDordrecht 12:52+3 min+3 min
Fri 9 OctMiddelburg 13:58+1 min+1 min
Thu 8 OctMiddelburg 13:57Partial coverage0 min—
Wed 7 OctMiddelburg 13:57Partial coverage0 min—
Tue 6 OctMiddelburg 13:57Partial coverage0 min—
Mon 5 OctMiddelburg 13:580 min—
Sun 4 OctRotterdam Blaak 21:430 min—
Sat 3 OctRotterdam Blaak 23:32−1 min+15 min
Fri 2 OctRotterdam Blaak 23:27−1 min+3 min
Thu 1 OctRotterdam Blaak 22:440 min+3 min
Wed 30 SeptRotterdam Blaak 17:32−1 min+4 min
Tue 29 SeptRotterdam Blaak 23:53−4 min+2 min