Train NS 2972 Maastricht – Enkhuizen

Maastricht 18:59 → Enkhuizen 22:23 Daily 3 h 24 min · 16 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 18:59 from Maastricht · Mon 9 Nov

Next departure 18:59 Monday · Maastricht
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 24 full · 0 partial · 4 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 23 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: +4 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 16 Oct Max en route +13 min · last fix heading to Weert +12 min
  • Sat 10 Oct Max en route +10 min · last fix heading to Hoorn Kersenboogerd +10 min
  • Mon 12 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
18:59on time on time
19:16 / 19:17≈ on time ≈ on time
19:31 / 19:32≈ on time ≈ on time
19:46≈ on time ≈ +1 min
20:02 / 20:04≈ on time ≈ +1 min
20:23 / 20:24≈ on time ≈ +1 min
20:51 / 20:54≈ on time ≈ +1 min
21:12≈ on time ≈ +2 min
21:20 / 21:23≈ on time ≈ +2 min
21:28 / 21:30≈ on time ≈ +2 min
21:56 / 21:58≈ on time ≈ +2 min
22:02≈ on time ≈ +2 min
22:09≈ on time ≈ +2 min
22:14 / 22:16≈ on time ≈ +3 min
22:19≈ on time ≈ +3 min
22:23on 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
Fri 6 Nov— 22:240 min+5 min
Thu 5 Nov— 22:240 min—
Wed 4 Nov— 22:24+1 min+2 min
Tue 3 Nov— 22:390 min—
Mon 2 Nov— 22:240 min—
Sun 1 NovBovenkarspel Flora 22:340 min—
Sat 31 OctBovenkarspel Flora 22:330 min—
Fri 30 Oct— 22:510 min—
Thu 29 Oct— 22:24+1 min—
Wed 28 Oct— 22:250 min—
Tue 27 Oct— 20:340 min—
Mon 26 OctAmsterdam Centraal 22:250 min—
Sun 25 OctBovenkarspel Flora 22:33No data—
Fri 23 OctSittard 21:29+2 min+2 min
Thu 22 Oct— 22:250 min—
Wed 21 Oct— 22:290 min—
Tue 20 Oct— 19:530 min—
Mon 19 Oct— 23:290 min—
Sun 18 OctBovenkarspel Flora 22:34+1 min+2 min
Sat 17 OctBovenkarspel Flora 22:33No data—
Fri 16 OctWeert 22:36+12 min+13 min
Thu 15 Oct— 02:250 min—
Wed 14 OctWeert 22:24No data—
Tue 13 Oct— 22:25No data—
Mon 12 Oct— 22:33+5 min+5 min
Sun 11 OctBovenkarspel Flora 22:34+1 min—
Sat 10 OctHoorn Kersenboogerd 22:37+10 min+10 min
Fri 9 Oct— 22:240 min—
Thu 8 Oct— 22:250 min—
Wed 7 Oct— 22:240 min+2 min