Train NS 3937 Enkhuizen – Heerlen

Enkhuizen 09:39 → Heerlen 13: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 5 November 0 min

Next service: tomorrow 09:39 from Enkhuizen · Sat 7 Nov

Next departure 09:39 tomorrow · Enkhuizen
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 10 full · 5 partial · 4 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 35 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: 0 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 7 Oct Max en route +8 min · last fix heading to Sittard +8 min
  • Sat 24 Oct Max en route +7 min · last fix heading to Sittard +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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