Train NS 3925 Enkhuizen – Heerlen

Enkhuizen 06:39 → Heerlen 10:11 Daily 3 h 32 min · 16 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 10 November +7 min

Next service: today 06:39 from Enkhuizen · Wed 11 Nov

Next departure 06:39 today · Enkhuizen
On-time · 30 days
88%
23/26 runs under 3 min
RT coverage: 19 full · 7 partial · 3 no data
On-time · 90 days
88%
29/33 runs under 3 min
RT coverage: 26 full · 7 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Tue 10 Nov Max en route +7 min · last fix heading to Enkhuizen +7 min
  • Mon 26 Oct Max en route +5 min · last fix heading to Sittard +5 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Sittard +5 min
  • Sat 24 Oct Max en route +6 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 29
  • 3–10 min 12% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 83% T n=6
  • 100% W n=5
  • 100% T n=5
  • 67% F n=3
  • 80% 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, 33 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
06:39on time on time
06:43≈ on time ≈ on time
06:46 / 06:47≈ on time ≈ on time
06:51 / 06:52≈ on time ≈ on time
06:59≈ on time ≈ on time
07:03 / 07:09≈ on time ≈ on time
07:35≈ on time ≈ +1 min
07:41 / 07:44≈ on time ≈ +1 min
07:52≈ on time ≈ +1 min
08:11 / 08:14≈ on time ≈ +1 min
08:42 / 08:45≈ on time ≈ +2 min
09:05 / 09:08≈ on time ≈ +2 min
09:25≈ on time ≈ +3 min
09:38 / 09:40≈ on time ≈ +3 min
09:55 / 09:56≈ on time ≈ +3 min
10:11on time +3 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 NovEnkhuizen 10:24Partial coverage+7 min+7 min
Mon 9 NovSittard 10:09+1 min+1 min
Sun 8 NovVlissingen Souburg 10:490 min—
Sat 7 NovVlissingen Souburg 10:53+3 min+3 min
Fri 6 NovSittard 10:13No data—
Thu 5 NovSittard 10:19Partial coverage0 min—
Wed 4 NovSittard 10:09Partial coverage+1 min+8 min
Tue 3 NovSittard 10:09Partial coverage0 min—
Mon 2 NovSittard 10:330 min—
Sun 1 NovSittard 10:15+2 min+2 min
Sat 31 OctSittard 10:120 min—
Fri 30 OctSittard 10:190 min—
Thu 29 OctSittard 10:10Partial coverage0 min—
Wed 28 OctSittard 10:120 min—
Tue 27 OctSittard 10:15Partial coverage0 min—
Mon 26 OctSittard 10:10+5 min+5 min
Sun 25 OctSittard 10:16No data—
Sat 24 OctSittard 10:16+4 min+6 min
Fri 23 OctSittard 10:160 min—
Thu 22 OctSittard 10:110 min—
Wed 21 OctSittard 10:110 min—
Tue 20 OctSittard 10:12+1 min—
Mon 19 OctSittard 10:16Partial coverage0 min—
Sun 18 OctSittard 10:13+1 min—
Sat 17 OctSittard 10:15+2 min+2 min
Fri 16 OctSittard 10:12No data—
Thu 15 OctWeert 10:580 min—
Wed 14 OctSittard 10:120 min—
Tue 13 OctSittard 10:150 min—
Mon 12 OctSittard 10:210 min—