Train NS 3949 Enkhuizen – Heerlen

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

It does not run today

Last recorded run: Thursday 12 November +1 min

Next service: Monday 12:39 from Enkhuizen · Mon 16 Nov

Next departure 12:39 Monday · Enkhuizen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 9 full · 9 partial · 2 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 16 full · 9 partial · 30 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

  • Sun 8 Nov Max en route +13 min · last fix heading to Vlissingen Souburg +12 min
  • Wed 11 Nov Max en route +4 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 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 80% W n=5
  • 100% T n=6
  • 100% F n=1
  • 100% S n=2
  • 0% S n=1

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