Train NS 3954 Heerlen – Enkhuizen

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

✓ Today’s run finished

Today, last fix heading to Bovenkarspel Flora at 18:03 0 min

  1. Heerlen14:19
  2. Weert15:04
  3. 's-Hertogenbosch15:46
  4. Amsterdam Centraal16:45
  5. Hoorn17:21
  6. Bovenkarspel Flora17:49
  7. Enkhuizen17:53

Next service: tomorrow 14:19 from Heerlen · Wed 11 Nov

Next departure 14:19 tomorrow · Heerlen
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 18 full · 6 partial · 6 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 25 full · 6 partial · 55 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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