Train NS 3933 Enkhuizen – Vlissingen

Enkhuizen 08:39 → Vlissingen 12:39 Mon, Tue, Wed, Thu, Sat, Sun 4 h 00 min · 25 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Vlissingen Souburg at 12:49 +1 min

  1. Enkhuizen08:39
  2. Hoorn Kersenboogerd08:59
  3. Amsterdam Amstel09:52
  4. Breda11:11
  5. Rilland-Bath11:56
  6. Vlissingen Souburg12:36
  7. Vlissingen12:39

Next service: tomorrow 08:39 from Enkhuizen · Sun 8 Nov

Next departure 08:39 tomorrow · Enkhuizen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 16 full · 1 partial · 6 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 19 full · 1 partial · 45 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: +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

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 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
08:39on time on time
08:43≈ on time ≈ on time
08:46 / 08:47≈ on time ≈ on time
08:51 / 08:52≈ on time ≈ on time
08:59≈ on time ≈ on time
09:03 / 09:04≈ on time ≈ on time
09:30 / 09:34≈ on time ≈ on time
09:40 / 09:44≈ on time ≈ on time
09:52≈ on time ≈ on time
10:10 / 10:14≈ on time ≈ on time
10:41 / 10:43≈ on time ≈ on time
10:57 / 10:58≈ on time ≈ on time
11:11 / 11:15≈ on time ≈ on time
11:23≈ on time ≈ on time
11:33 / 11:36≈ on time ≈ on time
11:46≈ on time ≈ on time
11:56≈ on time ≈ on time
12:00≈ on time ≈ on time
12:06≈ on time ≈ on time
12:12≈ on time ≈ on time
12:17≈ on time ≈ on time
12:27≈ on time ≈ on time
12:32≈ on time ≈ on time
12:36≈ on time ≈ on time
12:39on 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 NovVlissingen Souburg 12:49Partial coverage+1 min+1 min
Thu 5 NovSittard 12:14No data—
Wed 4 NovSittard 12:090 min+1 min
Tue 3 NovSittard 12:12No data—
Mon 2 NovSittard 12:130 min—
Sun 1 NovEindhoven Centraal 12:130 min—
Thu 29 OctSittard 12:100 min—
Wed 28 OctSittard 12:120 min—
Tue 27 OctSittard 12:11No data—
Mon 26 OctSittard 12:120 min—
Sun 25 OctSittard 12:15No data—
Sat 24 OctSittard 12:120 min+1 min
Fri 23 OctSittard 12:120 min—
Thu 22 OctSittard 12:280 min—
Wed 21 OctSittard 12:120 min—
Tue 20 OctSittard 12:120 min—
Mon 19 OctSittard 12:190 min—
Sun 18 OctSittard 12:15+1 min+2 min
Thu 15 OctSittard 12:17No data—
Wed 14 OctSittard 12:120 min—
Tue 13 OctSittard 12:15No data—
Mon 12 OctSittard 12:130 min—
Sun 11 OctSittard 12:130 min+2 min
Thu 8 OctSittard 12:130 min+1 min
Wed 7 OctSittard 12:130 min—
Tue 6 OctSittard 12:120 min+2 min
Mon 5 OctSittard 12:17No data—
Sun 4 OctSittard 12:10No data—
Thu 1 OctSittard 12:11No data—
Wed 30 SeptSittard 12:10No data—