Train NS 2976 Maastricht – Enkhuizen

Maastricht 20:01 → Enkhuizen 23:23 Daily 3 h 22 min · 16 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 20:01 from Maastricht · Thu 5 Nov

Next departure 20:01 today · Maastricht
On-time · 30 days
82%
18/22 runs under 3 min
RT coverage: 22 full · 0 partial · 5 no data
On-time · 90 days
83%
20/24 runs under 3 min
RT coverage: 24 full · 0 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Sun 1 Nov Max en route +18 min · last fix heading to Bovenkarspel Flora +18 min
  • Mon 12 Oct Max en route +22 min · last fix heading to — +16 min
  • Wed 14 Oct Max en route +14 min · last fix heading to — +9 min
  • Fri 23 Oct Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 20
  • 3–10 min 8% · 2
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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