Train NS 3972 Vlissingen – Enkhuizen

Vlissingen 18:20 → Enkhuizen 22:23 Daily 4 h 03 min · 25 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 18:20 from Vlissingen · Mon 9 Nov

Next departure 18:20 today · Vlissingen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 13 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 22 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
18:20on time on time
18:24≈ on time ≈ on time
18:29≈ on time ≈ on time
18:33≈ on time ≈ on time
18:43≈ on time ≈ on time
18:48≈ on time ≈ on time
18:54≈ on time ≈ on time
19:00≈ on time ≈ on time
19:04≈ on time ≈ on time
19:13 / 19:14≈ on time ≈ on time
19:24 / 19:27≈ on time ≈ +1 min
19:36≈ on time ≈ +1 min
19:44 / 19:49≈ on time ≈ +1 min
20:02 / 20:03≈ on time ≈ +1 min
20:18 / 20:20≈ on time ≈ +1 min
20:48 / 20:51≈ on time ≈ +1 min
21:10≈ on time ≈ +1 min
21:18 / 21:20≈ on time ≈ +1 min
21:26 / 21:30≈ on time ≈ +2 min
21:56 / 21:58≈ on time ≈ +2 min
22:02≈ on time ≈ +2 min
22:09≈ on time ≈ +2 min
22:14 / 22:16≈ on time ≈ +2 min
22:19≈ on time ≈ +2 min
22:23on time +2 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 22:34Partial coverage+1 min+1 min
Sat 7 NovBovenkarspel Flora 22:330 min—
Fri 6 Nov— 19:53+2 min+2 min
Thu 5 Nov— 19:53No data—
Wed 4 Nov— 19:530 min—
Tue 3 Nov— 19:52No data—
Mon 2 Nov— 19:520 min—
Sun 1 NovWeert 19:490 min—
Sat 31 OctWeert 19:520 min—
Fri 30 OctHeerlen 19:52No data—
Thu 29 Oct— 19:530 min+2 min
Wed 28 Oct— 19:520 min—
Tue 27 Oct— 19:55No data—
Mon 26 OctWeert 20:03No data—
Sun 25 OctWeert 20:07No data—
Sat 24 OctBovenkarspel Flora 22:340 min—
Fri 23 OctRoermond 19:56+2 min+4 min
Thu 22 Oct— 19:530 min—
Wed 21 Oct— 19:53No data—
Tue 20 Oct— 19:37No data—
Mon 19 Oct— 19:53No data—
Sun 18 OctWeert 19:520 min—
Sat 17 OctWeert 19:530 min—
Fri 16 OctWeert 19:52No data—
Thu 15 Oct— 19:52No data—
Wed 14 OctWeert 19:52No data—
Tue 13 Oct— 19:55No data—
Mon 12 Oct— 19:520 min—
Sun 11 OctWeert 19:520 min—
Sat 10 OctWeert 19:520 min—