Train NS 3920 Heerlen – Enkhuizen

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 05:49 from Heerlen · Wed 11 Nov

Next departure 05:49 today · Heerlen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 13 full · 9 partial · 1 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 17 full · 10 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 29 Oct Max en route +3 min · last fix heading to Bovenkarspel Flora +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 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=6
  • 100% W n=5
  • 80% T n=5
  • 100% F n=4
  • 100% S n=2
  • — S n=0

Stops and timetable

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

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