Train NS 3975 Enkhuizen – Vlissingen

Enkhuizen 19:09 → Vlissingen 23:10 Daily 4 h 01 min · 25 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 19:09 from Enkhuizen · Mon 9 Nov

Next departure 19:09 today · Enkhuizen
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 13 full · 1 partial · 13 no data
On-time · 90 days
80%
16/20 runs under 3 min
RT coverage: 19 full · 1 partial · 30 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Sat 7 Nov Max en route +13 min · last fix heading to Vlissingen Souburg +10 min
  • Thu 8 Oct Max en route +5 min · last fix heading to — +5 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +4 min
  • Fri 6 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 16
  • 3–10 min 20% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
19:09on time +1 min
19:13≈ on time ≈ +1 min
19:16 / 19:17≈ on time ≈ +1 min
19:21 / 19:22≈ on time ≈ +1 min
19:29≈ on time ≈ +1 min
19:33 / 19:34≈ on time ≈ +1 min
20:00 / 20:04≈ on time ≈ +1 min
20:10 / 20:12≈ on time ≈ +1 min
20:20≈ on time ≈ +2 min
20:39 / 20:44≈ +1 min ≈ +2 min
21:11 / 21:13≈ +1 min ≈ +3 min
21:27 / 21:28≈ +1 min ≈ +3 min
21:41 / 21:45≈ +1 min ≈ +3 min
21:53≈ +1 min ≈ +3 min
22:03 / 22:06≈ +1 min ≈ +3 min
22:16≈ +1 min ≈ +4 min
22:26≈ +1 min ≈ +4 min
22:30≈ +1 min ≈ +4 min
22:36≈ +1 min ≈ +4 min
22:42≈ +1 min ≈ +4 min
22:47≈ +1 min ≈ +4 min
22:57≈ +1 min ≈ +4 min
23:02≈ +1 min ≈ +4 min
23:06≈ +1 min ≈ +4 min
23:10+1 min +4 min

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
Sun 8 NovVlissingen Souburg 23:19Partial coverage+1 min+1 min
Sat 7 NovVlissingen Souburg 23:19+10 min+13 min
Fri 6 Nov— 22:44+4 min+4 min
Thu 5 Nov— 22:44No data—
Wed 4 Nov— 22:44+1 min+2 min
Mon 2 Nov— 22:420 min+1 min
Sun 1 NovSittard 22:43+2 min+2 min
Sat 31 OctSittard 22:420 min—
Fri 30 Oct— 22:42No data—
Thu 29 Oct— 22:46+1 min+1 min
Wed 28 Oct— 22:46No data—
Tue 27 Oct— 22:44No data—
Mon 26 Oct— 22:44No data—
Sun 25 OctSittard 22:46No data—
Sat 24 OctSittard 22:450 min—
Fri 23 Oct— 22:47+2 min+2 min
Thu 22 Oct— 22:47No data—
Wed 21 Oct— 22:46No data—
Tue 20 Oct— 22:46No data—
Sun 18 OctSittard 22:45+2 min+2 min
Sat 17 OctSittard 22:40No data—
Fri 16 Oct— 22:46+4 min+5 min
Thu 15 Oct— 22:42No data—
Wed 14 Oct— 22:45No data—
Tue 13 Oct— 22:43No data—
Mon 12 Oct— 22:43+1 min+1 min
Sun 11 OctSittard 22:42+1 min+1 min
Sat 10 Oct— 22:47+3 min+3 min
Fri 9 Oct— 22:45+1 min+2 min
Thu 8 Oct— 22:46+5 min+5 min