Train NS 2982 Maastricht – Enkhuizen

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 21:29 from Maastricht · Tue 10 Nov

Next departure 21:29 today · Maastricht
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 22 full · 4 partial · 0 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 27 full · 6 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 33 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
21:29on time on time
21:46 / 21:47≈ on time ≈ on time
22:01 / 22:02≈ on time ≈ on time
22:16≈ on time ≈ on time
22:32 / 22:34≈ on time ≈ on time
22:53 / 22:54≈ on time ≈ on time
23:21 / 23:24≈ on time ≈ on time
23:42≈ on time ≈ on time
23:50 / 23:53≈ on time ≈ on time
23:58 / 00:00≈ on time ≈ on time
00:26 / 00:28≈ on time ≈ on time
00:32≈ on time ≈ on time
00:39≈ on time ≈ on time
00:44 / 00:46≈ on time ≈ on time
00:49≈ on time ≈ on time
00:53on time on time

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
Sun 8 NovBovenkarspel Flora 01:03Partial coverage0 min—
Sat 7 Nov— 00:540 min—
Fri 6 Nov— 00:540 min—
Thu 5 Nov— 00:270 min—
Wed 4 Nov— 00:280 min—
Tue 3 Nov— 00:540 min—
Mon 2 Nov— 00:54+1 min—
Sun 1 NovBovenkarspel Flora 01:03Partial coverage0 min—
Sat 31 Oct's-Hertogenbosch 01:020 min—
Fri 30 Oct— 00:550 min—
Wed 28 Oct— 00:270 min—
Tue 27 Oct— 00:540 min—
Mon 26 Oct— 00:550 min—
Sun 25 OctBovenkarspel Flora 01:10Partial coverage0 min—
Fri 23 Oct— 00:01+3 min+4 min
Thu 22 Oct— 00:290 min—
Wed 21 Oct— 00:290 min—
Tue 20 Oct— 23:420 min—
Mon 19 Oct— 01:350 min+3 min
Sun 18 OctBovenkarspel Flora 01:04Partial coverage0 min+4 min
Sat 17 OctBovenkarspel Flora 01:030 min—
Fri 16 Oct— 00:540 min—
Thu 15 Oct— 00:340 min—
Wed 14 Oct— 00:270 min—
Tue 13 Oct— 00:550 min—
Mon 12 Oct— 00:550 min+4 min
Sun 11 OctBovenkarspel Flora 01:04Partial coverage0 min—
Sat 10 OctRoermond 00:590 min+2 min
Fri 9 Oct— 00:540 min—
Thu 8 Oct— 00:270 min—