Train NS 3932 Heerlen – Enkhuizen

Heerlen 08:49 → Enkhuizen 12:23 Mon, Tue, Wed, Thu, Sat, Sun 3 h 34 min · 16 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 12 November 0 min

Next service: Monday 08:49 from Heerlen · Mon 16 Nov

Next departure 08:49 Monday · Heerlen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 7 full · 11 partial · 2 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 10 full · 14 partial · 31 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 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

  • Wed 11 Nov Max en route +4 min · last fix heading to Bovenkarspel Flora +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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:49on time on time
09:04 / 09:05≈ on time ≈ on time
09:19 / 09:20≈ on time ≈ on time
09:34≈ on time ≈ on time
09:51 / 09:56≈ on time ≈ on time
10:16 / 10:20≈ on time ≈ on time
10:46 / 10:49≈ on time ≈ +1 min
11:07≈ on time ≈ +1 min
11:15 / 11:18≈ on time ≈ +1 min
11:24≈ on time ≈ +1 min
11:51 / 11:58≈ on time ≈ +1 min
12:02≈ on time ≈ +1 min
12:09≈ on time ≈ +1 min
12:14 / 12:16≈ on time ≈ +1 min
12:19≈ on time ≈ +1 min
12:23on 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
Thu 12 NovBovenkarspel Flora 12:33Partial coverage0 min—
Wed 11 NovBovenkarspel Flora 12:34+4 min+4 min
Tue 10 NovBovenkarspel Flora 12:34Partial coverage+1 min—
Mon 9 NovBovenkarspel Flora 12:34Partial coverage+1 min—
Sun 8 NovBovenkarspel Flora 12:34+1 min—
Sat 7 NovBovenkarspel Flora 12:330 min—
Thu 5 NovBovenkarspel Flora 12:34No data—
Wed 4 NovBovenkarspel Flora 12:34Partial coverage0 min—
Tue 3 NovBovenkarspel Flora 12:33No data—
Mon 2 NovBovenkarspel Flora 12:34Partial coverage0 min—
Thu 29 OctBovenkarspel Flora 12:34Partial coverage0 min—
Wed 28 OctBovenkarspel Flora 12:330 min—
Tue 27 OctBovenkarspel Flora 12:340 min—
Mon 26 OctBovenkarspel Flora 12:34Partial coverage0 min—
Sat 24 OctBovenkarspel Flora 12:340 min—
Fri 23 OctBovenkarspel Flora 12:440 min—
Thu 22 OctBovenkarspel Flora 12:34Partial coverage0 min—
Wed 21 OctBovenkarspel Flora 12:53Partial coverage0 min—
Tue 20 OctBovenkarspel Flora 12:34Partial coverage0 min—
Mon 19 OctBovenkarspel Flora 12:34Partial coverage0 min—
Thu 15 OctBovenkarspel Flora 12:34Partial coverage0 min—
Wed 14 OctBovenkarspel Flora 12:33Partial coverage0 min—
Tue 13 OctBovenkarspel Flora 12:34No data—
Mon 12 OctBovenkarspel Flora 12:34Partial coverage0 min—
Thu 8 OctBovenkarspel Flora 12:34+1 min—
Wed 7 OctBovenkarspel Flora 12:340 min—
Tue 6 OctBovenkarspel Flora 12:34+1 min—
Mon 5 OctWeert 09:49No data—
Thu 1 OctBovenkarspel Flora 12:34No data—
Wed 30 SeptBovenkarspel Flora 12:33No data—