Train NS 3927 Enkhuizen – Heerlen

Enkhuizen 07:09 → Heerlen 10:41 Daily 3 h 32 min · 16 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 10:43 No data

  1. Enkhuizen07:09
  2. Hoogkarspel07:21
  3. Hoorn07:33
  4. Amsterdam Amstel08:22
  5. 's-Hertogenbosch09:12
  6. Sittard10:25
  7. Heerlen10:41

Next service: tomorrow 07:09 from Enkhuizen · Fri 6 Nov

Next departure 07:09 tomorrow · Enkhuizen
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 25 full · 3 partial · 2 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 26 full · 3 partial · 58 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: +3 min

Last 30 days

Arrival delay at Heerlen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +8 min · last fix heading to Sittard +7 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Roermond +4 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Sittard +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 80% W n=5
  • 100% T n=4
  • 75% F n=4
  • 75% 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, 29 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
07:09on time on time
07:13≈ on time ≈ on time
07:16 / 07:17≈ on time ≈ on time
07:21 / 07:22≈ on time ≈ on time
07:29≈ on time ≈ on time
07:33 / 07:39≈ on time ≈ on time
08:05≈ on time ≈ +1 min
08:11 / 08:14≈ on time ≈ +1 min
08:22≈ on time ≈ +1 min
08:41 / 08:44≈ on time ≈ +1 min
09:12 / 09:15≈ on time ≈ +1 min
09:35 / 09:38≈ on time ≈ +1 min
09:55≈ on time ≈ +1 min
10:08 / 10:10≈ on time ≈ +2 min
10:25 / 10:26≈ on time ≈ +2 min
10:41on 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
Thu 5 NovSittard 10:43No data—
Wed 4 NovRoermond 10:24Partial coverage+4 min+4 min
Tue 3 NovSittard 10:54Partial coverage0 min—
Mon 2 NovSittard 10:420 min—
Sun 1 NovSittard 10:450 min+2 min
Sat 31 OctSittard 10:46+1 min+3 min
Fri 30 OctSittard 10:400 min—
Thu 29 OctSittard 10:400 min—
Wed 28 OctSittard 10:450 min—
Tue 27 OctSittard 10:420 min—
Mon 26 OctSittard 10:410 min—
Sun 25 OctSittard 10:42No data—
Sat 24 OctSittard 10:46+2 min+3 min
Fri 23 OctSittard 10:460 min—
Thu 22 OctSittard 10:520 min—
Wed 21 OctSittard 10:440 min—
Tue 20 OctSittard 10:400 min—
Mon 19 OctSittard 10:44Partial coverage0 min—
Sun 18 OctSittard 10:450 min+3 min
Sat 17 OctSittard 10:450 min—
Fri 16 OctSittard 10:430 min—
Thu 15 OctEindhoven Centraal 10:580 min—
Wed 14 OctSittard 10:420 min—
Tue 13 OctSittard 10:450 min—
Mon 12 OctSittard 10:450 min—
Sun 11 OctSittard 10:42+1 min+1 min
Sat 10 OctSittard 10:46+3 min+7 min
Fri 9 OctSittard 10:49+7 min+8 min
Thu 8 OctSittard 10:45+1 min+1 min
Wed 7 OctSittard 12:020 min—