Train NS 3662 Vlissingen – Arnhem Centraal

Vlissingen 17:18 → Arnhem Centraal 20:09 Daily 2 h 51 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to 's-Hertogenbosch at 20:11 +8 min

  1. Vlissingen17:18
  2. Arnemuiden17:31
  3. Kruiningen-Yerseke17:52
  4. Bergen op Zoom18:12
  5. 's-Hertogenbosch19:20
  6. Oss19:38
  7. Arnhem Centraal20:09

Next service: Monday 17:18 from Vlissingen · Mon 26 Oct

Next departure 17:18 Monday · Vlissingen
On-time · 30 days
46%
6/13 runs under 3 min
RT coverage: 11 full · 2 partial · 17 no data
On-time · 90 days
46%
6/13 runs under 3 min
RT coverage: 11 full · 2 partial · 76 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: +4 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Arnhem 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

  • Fri 9 Oct Max en route +15 min · last fix heading to Roosendaal +15 min
  • Fri 23 Oct Max en route +8 min · last fix heading to 's-Hertogenbosch +8 min
  • Tue 6 Oct Max en route +10 min · last fix heading to Rilland-Bath +8 min
  • Fri 16 Oct Max en route +8 min · last fix heading to Nijmegen +8 min
  • Thu 8 Oct Max en route +7 min · last fix heading to Rilland-Bath +7 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 46% · 6
  • 3–10 min 46% · 6
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
17:18
17:22
17:26
17:31
17:41
17:46
17:52
17:58
18:02
18:12
18:22 / 18:27
18:37
18:45 / 18:49
19:02 / 19:04
19:20 / 19:26
19:38
19:54 / 19:56
20:09

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
Fri 23 Oct's-Hertogenbosch 20:11Partial coverage+8 min+8 min
Thu 22 OctEtten-Leur 20:29No data—
Wed 21 OctEtten-Leur 20:11No data—
Tue 20 OctEtten-Leur 20:23Partial coverage0 min—
Mon 19 OctEtten-Leur 19:210 min—
Sun 18 OctWijhe 21:17+4 min+4 min
Sat 17 OctWijhe 21:14No data—
Fri 16 OctNijmegen 21:23+8 min+8 min
Thu 15 OctRoosendaal 21:17No data—
Wed 14 OctOss 21:11No data—
Tue 13 OctEtten-Leur 21:16No data—
Mon 12 OctEtten-Leur 21:160 min—
Sun 11 OctWijhe 21:19+6 min+6 min
Sat 10 OctWijhe 21:130 min—
Fri 9 OctRoosendaal 20:38+15 min+15 min
Thu 8 OctRilland-Bath 21:17+7 min+7 min
Wed 7 OctRilland-Bath 21:12+1 min—
Tue 6 OctRilland-Bath 21:26+8 min+10 min
Mon 5 OctBergen op Zoom 21:16+1 min+2 min
Sun 4 OctWijhe 21:22No data—
Sat 3 OctWijhe 21:14No data—
Fri 2 OctEtten-Leur 18:51No data—
Thu 1 OctRilland-Bath 18:16No data—
Wed 30 SeptRilland-Bath 18:16No data—
Tue 29 SeptRilland-Bath 18:16No data—
Mon 28 SeptRilland-Bath 18:16No data—
Sun 27 SeptWijhe 21:13No data—
Sat 26 SeptWijhe 21:13No data—
Fri 25 SeptRoosendaal 18:41No data—
Thu 24 SeptKruiningen-Yerseke 18:07No data—