Train NS 3936 Heerlen – Enkhuizen

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

✓ Today’s run finished

Today, last fix heading to Bovenkarspel Flora at 13:33 No data

  1. Heerlen09:49
  2. Weert10:34
  3. 's-Hertogenbosch11:16
  4. Amsterdam Centraal12:15
  5. Hoorn12:51
  6. Bovenkarspel Flora13:19
  7. Enkhuizen13:23

Next service: Saturday 09:49 from Heerlen · Sat 7 Nov

Next departure 09:49 Saturday · Heerlen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 7 full · 4 partial · 9 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 8 full · 4 partial · 41 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: 0 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

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=1
  • 100% S n=1
  • — S n=0

Stops and timetable

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

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