Train NS 3929 Enkhuizen – Heerlen

Enkhuizen 07:39 → Heerlen 11:11 Mon, Tue, Wed, Thu, Sat, Sun 3 h 32 min · 16 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 11:18 +3 min

  1. Enkhuizen07:39
  2. Hoogkarspel07:51
  3. Hoorn08:03
  4. Amsterdam Amstel08:52
  5. 's-Hertogenbosch09:42
  6. Sittard10:55
  7. Heerlen11:11

Next service: tomorrow 07:39 from Enkhuizen · Tue 10 Nov

Next departure 07:39 tomorrow · Enkhuizen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 17 full · 4 partial · 6 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 21 full · 4 partial · 50 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: +2 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Sittard +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Sittard +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 75% W n=4
  • 100% T n=3
  • 100% F n=1
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 25 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:39on time on time
07:43≈ on time ≈ on time
07:46 / 07:47≈ on time ≈ on time
07:51 / 07:52≈ on time ≈ on time
07:59≈ on time ≈ on time
08:03 / 08:09≈ on time ≈ on time
08:35≈ on time ≈ on time
08:41 / 08:44≈ on time ≈ on time
08:52≈ on time ≈ on time
09:11 / 09:14≈ on time ≈ on time
09:42 / 09:45≈ on time ≈ +1 min
10:05 / 10:08≈ on time ≈ +1 min
10:25≈ on time ≈ +1 min
10:38 / 10:40≈ on time ≈ +1 min
10:55 / 10:56≈ on time ≈ +1 min
11:11on 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
Mon 9 NovSittard 11:18Partial coverage+3 min+3 min
Sun 8 NovVlissingen Souburg 11:490 min—
Sat 7 NovVlissingen Souburg 11:49+1 min+1 min
Thu 5 NovSittard 11:24No data—
Wed 4 NovSittard 11:48+4 min+4 min
Tue 3 NovSittard 11:19No data—
Mon 2 NovSittard 11:130 min—
Sun 1 NovSittard 11:150 min—
Sat 31 OctSittard 11:120 min—
Thu 29 OctSittard 11:10Partial coverage0 min—
Wed 28 OctSittard 11:16Partial coverage0 min—
Tue 27 OctSittard 11:100 min—
Mon 26 OctSittard 11:100 min—
Sun 25 OctSittard 11:13No data—
Sat 24 OctSittard 11:130 min+1 min
Fri 23 OctSittard 11:230 min—
Thu 22 OctSittard 11:240 min—
Wed 21 OctSittard 11:12No data—
Tue 20 OctSittard 11:12No data—
Mon 19 OctSittard 11:24Partial coverage0 min—
Sun 18 OctSittard 11:16+2 min+2 min
Sat 17 OctSittard 11:120 min—
Thu 15 OctSittard 11:13No data—
Wed 14 OctSittard 11:120 min—
Tue 13 OctSittard 11:150 min—
Mon 12 OctSittard 11:120 min—
Sun 11 OctSittard 11:150 min—
Sat 10 OctSittard 11:13+1 min+2 min
Thu 8 OctSittard 11:120 min—
Wed 7 OctWeert 12:010 min+1 min