Train NS 3952 Heerlen – Enkhuizen

Heerlen 13:49 → Enkhuizen 17: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 +1 min

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

Next departure 13:49 Monday · Heerlen
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 11 full · 8 partial · 1 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 17 full · 9 partial · 29 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: +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

Worst days

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

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 92% · 24
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 83% W n=6
  • 100% T n=5
  • — F n=0
  • 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, 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
13:49on time on time
14:04 / 14:05≈ on time ≈ on time
14:19 / 14:20≈ on time ≈ +1 min
14:34≈ on time ≈ +1 min
14:51 / 14:56≈ on time ≈ +1 min
15:16 / 15:20≈ on time ≈ +2 min
15:46 / 15:49≈ on time ≈ +2 min
16:07≈ on time ≈ +3 min
16:15 / 16:18≈ on time ≈ +3 min
16:24≈ on time ≈ +3 min
16:51 / 16:58≈ on time ≈ +4 min
17:02≈ on time ≈ +4 min
17:09≈ on time ≈ +4 min
17:14 / 17:16≈ on time ≈ +4 min
17:19≈ on time ≈ +4 min
17:23on time +4 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 17:33Partial coverage+1 min+1 min
Wed 11 NovBovenkarspel Flora 17:33+11 min+11 min
Tue 10 NovBovenkarspel Flora 17:33Partial coverage0 min—
Mon 9 NovBovenkarspel Flora 17:33+9 min+9 min
Sun 8 NovBovenkarspel Flora 17:330 min—
Sat 7 NovBovenkarspel Flora 17:340 min—
Thu 5 NovBovenkarspel Flora 17:33Partial coverage0 min—
Wed 4 NovBovenkarspel Flora 17:330 min—
Tue 3 NovBovenkarspel Flora 17:33Partial coverage0 min—
Mon 2 NovWeert 17:440 min—
Thu 29 OctBovenkarspel Flora 17:33Partial coverage0 min—
Wed 28 OctBovenkarspel Flora 17:330 min—
Tue 27 OctBovenkarspel Flora 17:33Partial coverage0 min—
Mon 26 OctBovenkarspel Flora 17:330 min—
Sat 24 OctBovenkarspel Flora 17:340 min—
Fri 23 OctBovenkarspel Flora 17:35No data—
Thu 22 OctBovenkarspel Flora 17:33Partial coverage0 min—
Wed 21 OctBovenkarspel Flora 17:340 min—
Tue 20 OctBovenkarspel Flora 17:34Partial coverage0 min—
Mon 19 OctBovenkarspel Flora 17:460 min—
Thu 15 OctBovenkarspel Flora 17:33No data—
Wed 14 OctBovenkarspel Flora 17:340 min—
Tue 13 OctBovenkarspel Flora 17:33Partial coverage0 min—
Mon 12 OctBovenkarspel Flora 17:340 min—
Thu 8 OctBovenkarspel Flora 17:36+1 min—
Wed 7 OctBovenkarspel Flora 17:330 min—
Tue 6 OctBovenkarspel Flora 17:330 min—
Mon 5 OctWeert 14:52+1 min+1 min
Thu 1 OctBovenkarspel Flora 17:33No data—
Wed 30 SeptBovenkarspel Flora 17:33No data—