Train NS 3665 Arnhem Centraal – Vlissingen

Arnhem Centraal 19:23 → Vlissingen 22:10 Daily 2 h 47 min · 18 stops NS (Nederlandse Spoorwegen)

Running now · updated 20:01

Heading to Vlissingen No data

Estimated arrival at Vlissingen 22:10 · 115 km/h

  1. Arnhem Centraal19:23
  2. 's-Hertogenbosch20:05
  3. Etten-Leur20:53
  4. Rilland-Bath21:25
  5. Kruiningen-Yerseke21:35
  6. Arnemuiden21:56
  7. Vlissingen22:10
On-time · 30 days
62%
8/13 runs under 3 min
RT coverage: 13 full · 0 partial · 10 no data
On-time · 90 days
62%
8/13 runs under 3 min
RT coverage: 13 full · 0 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Fri 9 Oct Max en route +11 min · last fix heading to Olst +10 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Oss +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Middelburg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 62% · 8
  • 3–10 min 31% · 4
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 50% T n=2
  • 0% W n=1
  • 100% T n=1
  • 0% F n=2
  • 50% S n=2
  • 100% S n=2

Stops and timetable

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

StopSched.Today
19:23
19:36 / 19:38
19:53 / 19:54
20:05 / 20:11
20:26 / 20:28
20:40 / 20:45
20:53
21:03 / 21:06
21:15
21:25
21:30
21:35
21:41
21:46
21:56
22:01
22:06
22:10

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 21 Oct— 19:59No data—
Tue 20 Oct— 22:120 min—
Mon 19 OctOlst 18:500 min—
Sun 18 OctVlissingen Souburg 22:210 min—
Sat 17 OctVlissingen Souburg 22:370 min—
Fri 16 OctOss 22:17+4 min+5 min
Thu 15 OctWijhe 20:46No data—
Wed 14 OctNijmegen 22:17No data—
Tue 13 OctOlst 22:12No data—
Mon 12 OctDeventer 19:390 min—
Sun 11 OctVlissingen Souburg 22:210 min—
Sat 10 OctMiddelburg 22:18+3 min+4 min
Fri 9 OctOlst 22:31+10 min+11 min
Thu 8 Oct— 22:17+1 min+3 min
Wed 7 Oct— 22:17+4 min+4 min
Tue 6 Oct— 22:17+4 min+4 min
Mon 5 Oct— 22:110 min—
Sun 4 OctEtten-Leur 21:10No data—
Sat 3 OctEtten-Leur 21:10No data—
Fri 2 OctDeventer 18:59No data—
Sun 27 SeptVlissingen Souburg 22:42No data—
Sat 26 SeptVlissingen Souburg 22:20No data—
Fri 25 SeptWijhe 18:43No data—
Sun 20 SeptVlissingen Souburg 22:25No data—
Sat 19 SeptVlissingen Souburg 22:20No data—
Fri 18 SeptDeventer 18:59No data—
Sun 13 SeptVlissingen Souburg 22:21No data—
Sat 12 SeptVlissingen Souburg 22:20No data—
Fri 11 SeptDeventer 18:59No data—
Mon 7 SeptZwolle 18:34No data—