Train NS 2966 Maastricht – Enkhuizen

Maastricht 17:29 → Enkhuizen 20:53 Daily 3 h 24 min · 16 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 17:29 from Maastricht · Mon 9 Nov

Next departure 17:29 Monday · Maastricht
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 20 full · 2 partial · 6 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 24 full · 2 partial · 58 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: +1 min

Last 30 days

Arrival delay at Enkhuizen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 23 Oct Max en route +5 min · last fix heading to 's-Hertogenbosch +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=5
  • 80% F n=5
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 26 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
17:29on time on time
17:46 / 17:47≈ on time ≈ on time
18:01 / 18:02≈ on time ≈ on time
18:16≈ on time ≈ on time
18:32 / 18:34≈ on time ≈ on time
18:53 / 18:54≈ on time ≈ on time
19:21 / 19:24≈ on time ≈ on time
19:42≈ on time ≈ +1 min
19:50 / 19:53≈ on time ≈ +1 min
19:58 / 20:00≈ on time ≈ +1 min
20:26 / 20:28≈ on time ≈ +1 min
20:32≈ on time ≈ +1 min
20:39≈ on time ≈ +1 min
20:44 / 20:46≈ on time ≈ +1 min
20:49≈ on time ≈ +1 min
20:53on 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
Fri 6 NovEindhoven Centraal 20:54Partial coverage+1 min—
Thu 5 NovRoermond 20:550 min—
Wed 4 NovRoermond 20:54+1 min+2 min
Tue 3 NovRoermond 20:54No data—
Mon 2 NovRoermond 18:140 min—
Sun 1 NovBovenkarspel Flora 21:04+1 min—
Sat 31 OctBovenkarspel Flora 21:040 min—
Fri 30 Oct's-Hertogenbosch 21:06Partial coverage0 min—
Thu 29 OctRoermond 20:540 min—
Wed 28 OctRoermond 20:550 min—
Tue 27 OctRoermond 20:55No data—
Mon 26 OctRoermond 20:540 min—
Sun 25 OctBovenkarspel Flora 21:04No data—
Fri 23 Oct's-Hertogenbosch 20:02+5 min+5 min
Thu 22 OctEindhoven Centraal 19:350 min—
Wed 21 OctEindhoven Centraal 20:55No data—
Tue 20 OctEindhoven Centraal 18:480 min—
Mon 19 OctEindhoven Centraal 21:110 min—
Sun 18 OctBovenkarspel Flora 21:04+1 min—
Sat 17 OctBovenkarspel Flora 21:040 min—
Fri 16 OctAmsterdam Centraal 20:59+3 min+5 min
Thu 15 OctWeert 20:570 min—
Wed 14 OctAmsterdam Amstel 20:54No data—
Tue 13 OctEindhoven Centraal 21:07No data—
Mon 12 OctEindhoven Centraal 20:540 min—
Sun 11 OctBovenkarspel Flora 21:05+1 min+5 min
Sat 10 OctBovenkarspel Flora 21:07+1 min+5 min
Fri 9 OctEindhoven Centraal 20:540 min—
Thu 8 OctRoermond 21:050 min—
Wed 7 OctMaastricht 01:280 min+1 min