Train NS 3950 Heerlen – Enkhuizen

Heerlen 13:19 → Enkhuizen 16:53 Daily 3 h 34 min · 16 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:19 from Heerlen · Fri 6 Nov

Next departure 13:19 today · Heerlen
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 18 full · 5 partial · 6 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 21 full · 5 partial · 60 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

  • Thu 8 Oct Max en route +12 min · last fix heading to Bovenkarspel Flora +11 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 96% · 25
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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:19on time on time
13:34 / 13:35≈ on time ≈ on time
13:49 / 13:50≈ on time ≈ on time
14:04≈ on time ≈ on time
14:21 / 14:26≈ on time ≈ on time
14:46 / 14:50≈ on time ≈ +1 min
15:16 / 15:19≈ on time ≈ +1 min
15:37≈ on time ≈ +1 min
15:45 / 15:48≈ on time ≈ +1 min
15:54≈ on time ≈ +1 min
16:21 / 16:28≈ on time ≈ +1 min
16:32≈ on time ≈ +1 min
16:39≈ on time ≈ +1 min
16:44 / 16:46≈ on time ≈ +1 min
16:49≈ on time ≈ +1 min
16:53on 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 5 NovBovenkarspel Flora 17:03No data—
Wed 4 NovBovenkarspel Flora 17:04Partial coverage0 min—
Tue 3 NovBovenkarspel Flora 17:03No data—
Mon 2 NovBovenkarspel Flora 17:04No data—
Sun 1 NovWeert 14:200 min—
Sat 31 OctWeert 14:230 min—
Fri 30 OctWeert 14:23No data—
Thu 29 OctBovenkarspel Flora 17:080 min—
Wed 28 OctBovenkarspel Flora 17:03Partial coverage0 min—
Tue 27 OctBovenkarspel Flora 17:030 min—
Mon 26 OctBovenkarspel Flora 17:030 min—
Sun 25 OctWeert 14:27No data—
Sat 24 OctBovenkarspel Flora 17:04+1 min—
Fri 23 OctBovenkarspel Flora 17:040 min—
Thu 22 OctBovenkarspel Flora 17:03Partial coverage0 min—
Wed 21 OctBovenkarspel Flora 17:120 min—
Tue 20 OctBovenkarspel Flora 17:07Partial coverage0 min—
Mon 19 OctBovenkarspel Flora 17:040 min—
Sun 18 OctWeert 14:25+1 min+3 min
Sat 17 OctWeert 14:220 min—
Fri 16 OctWeert 14:220 min—
Thu 15 OctBovenkarspel Flora 17:030 min—
Wed 14 OctBovenkarspel Flora 17:03No data—
Tue 13 OctBovenkarspel Flora 17:04Partial coverage0 min—
Mon 12 OctBovenkarspel Flora 17:040 min—
Sun 11 OctWeert 14:220 min—
Sat 10 OctWeert 14:24+1 min+1 min
Fri 9 OctWeert 14:23+1 min+1 min
Thu 8 OctBovenkarspel Flora 17:03+11 min+12 min
Wed 7 OctBovenkarspel Flora 17:03+1 min—