Train NS 3939 Enkhuizen – Vlissingen

Enkhuizen 10:09 → Vlissingen 14:09 Daily 4 h 00 min · 25 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Vlissingen Souburg at 14:19 0 min

  1. Enkhuizen10:09
  2. Hoorn Kersenboogerd10:29
  3. Amsterdam Amstel11:20
  4. Breda12:41
  5. Rilland-Bath13:26
  6. Vlissingen Souburg14:06
  7. Vlissingen14:09

Next service: tomorrow 10:09 from Enkhuizen · Sun 8 Nov

Next departure 10:09 tomorrow · Enkhuizen
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 23 full · 1 partial · 6 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 18 Oct Max en route +6 min · last fix heading to Sittard +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
10:09on time on time
10:13≈ on time ≈ on time
10:16 / 10:17≈ on time ≈ on time
10:21 / 10:22≈ on time ≈ on time
10:29≈ on time ≈ on time
10:33 / 10:34≈ on time ≈ on time
11:00 / 11:04≈ on time ≈ on time
11:10 / 11:12≈ on time ≈ on time
11:20≈ on time ≈ on time
11:39 / 11:44≈ on time ≈ on time
12:11 / 12:13≈ on time ≈ +1 min
12:27 / 12:28≈ on time ≈ +1 min
12:41 / 12:45≈ on time ≈ +1 min
12:53≈ on time ≈ +1 min
13:03 / 13:06≈ on time ≈ +1 min
13:16≈ on time ≈ +1 min
13:26≈ on time ≈ +1 min
13:30≈ on time ≈ +1 min
13:36≈ on time ≈ +1 min
13:42≈ on time ≈ +1 min
13:47≈ on time ≈ +1 min
13:57≈ on time ≈ +1 min
14:02≈ on time ≈ +1 min
14:06≈ on time ≈ +1 min
14:09on time +1 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
Sat 7 NovVlissingen Souburg 14:19Partial coverage0 min—
Fri 6 NovSittard 13:42No data—
Thu 5 NovSittard 13:420 min—
Wed 4 NovSittard 13:44+1 min+1 min
Tue 3 NovSittard 13:390 min—
Mon 2 NovSittard 13:440 min—
Sun 1 NovSittard 13:43+4 min+4 min
Sat 31 OctSittard 13:420 min—
Fri 30 OctSittard 13:420 min—
Thu 29 OctSittard 13:400 min—
Wed 28 OctSittard 13:420 min—
Tue 27 OctSittard 13:410 min—
Mon 26 OctSittard 13:450 min—
Sun 25 OctSittard 13:51No data—
Sat 24 OctSittard 13:43+1 min+2 min
Fri 23 OctSittard 13:45No data—
Thu 22 OctSittard 13:460 min—
Wed 21 OctSittard 13:420 min—
Tue 20 OctSittard 13:420 min—
Mon 19 OctSittard 13:450 min—
Sun 18 OctSittard 13:46+5 min+6 min
Sat 17 OctSittard 13:45No data—
Fri 16 OctSittard 13:420 min—
Thu 15 OctSittard 13:42No data—
Wed 14 OctSittard 13:42No data—
Tue 13 OctSittard 13:430 min—
Mon 12 OctSittard 13:430 min—
Sun 11 OctSittard 13:420 min—
Sat 10 OctSittard 13:420 min+1 min
Fri 9 OctSittard 13:45+1 min+3 min