Train NS 3938 Vlissingen – Enkhuizen

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

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 09:50 from Vlissingen · Sun 8 Nov

Next departure 09:50 today · Vlissingen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 7 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 25 full · 1 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 26
  • 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=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 26 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
09:50on time on time
09:54≈ on time ≈ on time
09:59≈ on time ≈ on time
10:03≈ on time ≈ on time
10:13≈ on time ≈ on time
10:18≈ on time ≈ on time
10:24≈ on time ≈ on time
10:30≈ on time ≈ on time
10:34≈ on time ≈ on time
10:43 / 10:44≈ on time ≈ on time
10:54 / 10:57≈ on time ≈ on time
11:06≈ on time ≈ on time
11:14 / 11:19≈ on time ≈ on time
11:32 / 11:33≈ on time ≈ on time
11:48 / 11:50≈ on time ≈ on time
12:16 / 12:21≈ on time ≈ on time
12:40≈ on time ≈ on time
12:48 / 12:50≈ on time ≈ on time
12:56 / 13:00≈ on time ≈ on time
13:26 / 13:28≈ on time ≈ on time
13:32≈ on time ≈ on time
13:39≈ on time ≈ on time
13:44 / 13:46≈ on time ≈ on time
13:49≈ on time ≈ on time
13:53on time on time

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
Sat 7 NovBovenkarspel Flora 14:04Partial coverage+1 min+1 min
Fri 6 NovWeert 11:22No data—
Thu 5 NovBovenkarspel Flora 14:040 min—
Wed 4 NovBovenkarspel Flora 14:040 min—
Tue 3 NovSittard 18:020 min—
Mon 2 NovBovenkarspel Flora 14:040 min—
Sun 1 NovWeert 11:200 min—
Sat 31 OctWeert 11:190 min—
Fri 30 OctWeert 11:230 min—
Thu 29 OctBovenkarspel Flora 14:030 min—
Wed 28 OctBovenkarspel Flora 14:040 min—
Tue 27 OctBovenkarspel Flora 14:040 min—
Mon 26 OctBovenkarspel Flora 14:04No data—
Sun 25 OctWeert 11:22No data—
Sat 24 OctBovenkarspel Flora 14:040 min—
Fri 23 OctBovenkarspel Flora 14:050 min—
Thu 22 OctBovenkarspel Flora 14:040 min—
Wed 21 OctBovenkarspel Flora 14:030 min—
Tue 20 OctBovenkarspel Flora 14:040 min—
Mon 19 OctBovenkarspel Flora 14:040 min—
Sun 18 OctWeert 11:220 min—
Sat 17 OctWeert 11:250 min—
Fri 16 OctWeert 11:22No data—
Thu 15 OctBovenkarspel Flora 14:04No data—
Wed 14 OctBovenkarspel Flora 14:04No data—
Tue 13 OctBovenkarspel Flora 14:04No data—
Mon 12 OctBovenkarspel Flora 14:040 min—
Sun 11 OctWeert 11:23+1 min—
Sat 10 OctWeert 11:220 min—
Fri 9 OctWeert 11:23+1 min—