Train NS 3955 Enkhuizen – Heerlen

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 14:09 from Enkhuizen · Wed 11 Nov

Next departure 14:09 today · Enkhuizen
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 15 full · 6 partial · 8 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 23 full · 6 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Mon 26 Oct Max en route +9 min · last fix heading to Sittard +9 min
  • Mon 5 Oct Max en route +6 min · last fix heading to Sittard +6 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Sittard +4 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

  • 60% M n=5
  • 100% T n=4
  • 100% W n=3
  • 100% T n=5
  • 75% F n=4
  • 100% S n=5
  • 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
14:09on time on time
14:13≈ on time ≈ on time
14:16 / 14:17≈ on time ≈ on time
14:21 / 14:22≈ on time ≈ on time
14:29≈ on time ≈ on time
14:33 / 14:39≈ on time ≈ on time
15:05≈ on time ≈ +1 min
15:11 / 15:14≈ on time ≈ +1 min
15:22≈ on time ≈ +1 min
15:41 / 15:44≈ on time ≈ +1 min
16:12 / 16:15≈ on time ≈ +2 min
16:35 / 16:38≈ on time ≈ +2 min
16:55≈ on time ≈ +2 min
17:08 / 17:10≈ on time ≈ +2 min
17:25 / 17:26≈ on time ≈ +3 min
17:41on 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 NovSittard 17:43Partial coverage0 min—
Mon 9 NovSittard 17:44Partial coverage+1 min+2 min
Sun 8 NovVlissingen Souburg 18:19+1 min—
Sat 7 NovVlissingen Souburg 18:19+2 min+2 min
Fri 6 NovSittard 17:43+1 min+1 min
Thu 5 NovSittard 17:54Partial coverage0 min—
Wed 4 NovSittard 17:44+3 min+3 min
Tue 3 NovSittard 17:39No data—
Mon 2 NovHoorn 17:44No data—
Sun 1 NovSittard 17:40No data—
Sat 31 OctSittard 17:42+2 min+2 min
Fri 30 OctSittard 17:470 min—
Thu 29 OctSittard 17:330 min—
Wed 28 OctSittard 17:450 min—
Tue 27 OctSittard 17:46Partial coverage0 min—
Mon 26 OctSittard 17:51Partial coverage+9 min+9 min
Sun 25 OctSittard 17:46No data—
Sat 24 OctSittard 17:42+2 min+2 min
Fri 23 OctSittard 18:000 min—
Thu 22 OctSittard 17:400 min—
Wed 21 OctSittard 17:43No data—
Tue 20 OctSittard 17:410 min—
Mon 19 OctSittard 17:40Partial coverage0 min—
Sun 18 OctEindhoven Centraal 17:420 min—
Sat 17 OctEindhoven Centraal 17:560 min—
Fri 16 OctSittard 17:46No data—
Thu 15 OctSittard 17:450 min—
Wed 14 OctSittard 17:43No data—
Tue 13 OctSittard 17:43No data—
Mon 12 OctSittard 17:430 min—