Train NS 2978 Maastricht – Enkhuizen

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 20:29 from Maastricht · Sat 7 Nov

Next departure 20:29 today · Maastricht
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 1 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 18 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: 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

Worst days

  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 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
  • 75% F n=4
  • 100% S n=3
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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:29on time on time
20:46 / 20:47≈ on time ≈ on time
21:01 / 21:02≈ on time ≈ on time
21:16≈ on time ≈ on time
21:32 / 21:34≈ on time ≈ on time
21:53 / 21:54≈ on time ≈ on time
22:21 / 22:24≈ on time ≈ on time
22:42≈ on time ≈ on time
22:50 / 22:53≈ on time ≈ on time
22:58 / 23:00≈ on time ≈ on time
23:26 / 23:28≈ on time ≈ on time
23:32≈ on time ≈ on time
23:39≈ on time ≈ on time
23:44 / 23:46≈ on time ≈ on time
23:49≈ on time ≈ on time
23: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 Nov— 23:540 min—
Thu 5 Nov— 23:540 min—
Wed 4 Nov— 23:540 min—
Tue 3 Nov— 23:540 min—
Mon 2 Nov— 00:130 min+12 min
Sun 1 NovBovenkarspel Flora 00:040 min+7 min
Sat 31 OctAmsterdam Centraal 23:570 min—
Thu 29 Oct— 23:540 min—
Wed 28 Oct— 23:550 min—
Tue 27 Oct— 23:550 min—
Mon 26 Oct— 23:550 min—
Sun 25 OctBovenkarspel Flora 00:030 min—
Fri 23 Oct— 23:01+5 min+5 min
Thu 22 Oct— 23:540 min—
Wed 21 Oct— 23:550 min—
Tue 20 Oct— 21:240 min—
Mon 19 Oct— 22:580 min—
Sun 18 OctBovenkarspel Flora 00:040 min—
Sat 17 OctBovenkarspel Flora 00:030 min—
Fri 16 Oct— 23:580 min+3 min
Thu 15 Oct— 23:56No data—
Wed 14 Oct— 23:540 min—
Tue 13 Oct— 22:580 min—
Mon 12 Oct— 00:110 min+14 min
Sun 11 OctBovenkarspel Flora 00:030 min+3 min
Sat 10 Oct's-Hertogenbosch 00:030 min+8 min
Fri 9 Oct— 23:540 min+3 min
Thu 8 Oct— 23:55+1 min+3 min
Wed 7 Oct— 23:57+2 min+5 min
Tue 6 Oct— 23:540 min—