Train NS 3966 Vlissingen – Enkhuizen

Vlissingen 16:50 → Enkhuizen 20:53 Daily 4 h 03 min · 25 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 16:50 from Vlissingen · Mon 9 Nov

Next departure 16:50 today · Vlissingen
On-time · 30 days
77%
10/13 runs under 3 min
RT coverage: 11 full · 2 partial · 16 no data
On-time · 90 days
79%
15/19 runs under 3 min
RT coverage: 17 full · 2 partial · 67 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: +3 min

Last 30 days

Arrival delay at Enkhuizen, 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 +6 min · last fix heading to Weert +5 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Weert +5 min
  • Mon 26 Oct Max en route +3 min · last fix heading to Weert +3 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Weert +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 15
  • 3–10 min 21% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
16:50on time +1 min
16:54≈ on time ≈ +1 min
16:59≈ on time ≈ +2 min
17:03≈ on time ≈ +2 min
17:13≈ on time ≈ +2 min
17:18≈ on time ≈ +2 min
17:24≈ on time ≈ +2 min
17:30≈ on time ≈ +2 min
17:34≈ on time ≈ +2 min
17:43 / 17:44≈ on time ≈ +2 min
17:54 / 17:57≈ on time ≈ +2 min
18:06≈ on time ≈ +2 min
18:14 / 18:19≈ on time ≈ +2 min
18:32 / 18:33≈ on time ≈ +3 min
18:48 / 18:50≈ on time ≈ +3 min
19:16 / 19:21≈ on time ≈ +3 min
19:40≈ on time ≈ +3 min
19:48 / 19:50≈ on time ≈ +3 min
19:56 / 20:00≈ on time ≈ +3 min
20:26 / 20:28≈ on time ≈ +4 min
20:32≈ on time ≈ +4 min
20:39≈ on time ≈ +4 min
20:44 / 20:46≈ on time ≈ +4 min
20:49≈ on time ≈ +4 min
20:53on time +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 NovBovenkarspel Flora 21:03Partial coverage0 min—
Sat 7 NovBovenkarspel Flora 21:04Partial coverage0 min—
Fri 6 NovWeert 18:220 min—
Thu 5 NovWeert 18:22No data—
Wed 4 NovWeert 18:23No data—
Tue 3 NovWeert 18:23No data—
Mon 2 NovWeert 18:22No data—
Sun 1 NovWeert 18:220 min—
Sat 31 OctWeert 18:22+3 min+3 min
Fri 30 OctWeert 18:31No data—
Thu 29 OctRoermond 18:230 min—
Wed 28 OctWeert 18:22No data—
Tue 27 OctWeert 18:25No data—
Mon 26 OctWeert 18:31+3 min+3 min
Sun 25 OctWeert 18:25No data—
Sat 24 OctBovenkarspel Flora 21:040 min—
Fri 23 OctWeert 18:320 min—
Thu 22 OctWeert 18:22No data—
Wed 21 OctWeert 18:23No data—
Tue 20 OctWeert 18:180 min—
Mon 19 OctWeert 18:23No data—
Sun 18 OctWeert 18:230 min—
Sat 17 OctWeert 18:300 min—
Fri 16 OctWeert 18:22No data—
Thu 15 OctWeert 18:25No data—
Wed 14 OctWeert 18:23No data—
Tue 13 OctWeert 18:27No data—
Mon 12 OctWeert 18:23No data—
Sun 11 OctWeert 18:28+5 min+5 min
Sat 10 OctWeert 18:220 min—