Train NS 3930 Heerlen – Enkhuizen

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

✓ Today’s run finished

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

  1. Heerlen08:19
  2. Weert09:04
  3. 's-Hertogenbosch09:46
  4. Amsterdam Centraal10:45
  5. Hoorn11:21
  6. Bovenkarspel Flora11:49
  7. Enkhuizen11:53

Next service: tomorrow 08:19 from Heerlen · Fri 6 Nov

Next departure 08:19 tomorrow · Heerlen
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 15 full · 8 partial · 7 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 16 full · 8 partial · 63 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

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

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

Stops and timetable

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

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