Train NS 2975 Enkhuizen – Maastricht

Enkhuizen 19:09 → Maastricht 22:33 Daily 3 h 24 min · 16 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 22:43 +3 min

  1. Enkhuizen19:09
  2. Hoogkarspel19:21
  3. Hoorn19:33
  4. Amsterdam Amstel20:17
  5. 's-Hertogenbosch21:06
  6. Roermond22:00
  7. Maastricht22:33

Next service: Monday 19:09 from Enkhuizen · Mon 9 Nov

Next departure 19:09 Monday · Enkhuizen
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 19 full · 1 partial · 9 no data
On-time · 90 days
78%
18/23 runs under 3 min
RT coverage: 22 full · 1 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 min

Last 30 days

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

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

Worst days

  • Wed 4 Nov Max en route +33 min · last fix heading to — +33 min
  • Fri 16 Oct Max en route +11 min · last fix heading to Hoorn +11 min
  • Mon 5 Oct Max en route +8 min · last fix heading to — +7 min
  • Mon 12 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 9 Oct Max en route +8 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 18
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 4% · 1

On-time by weekday

  • 33% M n=3
  • 100% T n=2
  • 67% W n=3
  • 100% T n=5
  • 50% F n=4
  • 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, 23 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
19:09on time on time
19:13≈ on time ≈ on time
19:16 / 19:17≈ on time ≈ on time
19:21 / 19:22≈ on time ≈ +1 min
19:29≈ on time ≈ +1 min
19:33 / 19:34≈ on time ≈ +1 min
19:59 / 20:01≈ on time ≈ +3 min
20:07 / 20:09≈ on time ≈ +3 min
20:17≈ on time ≈ +4 min
20:36 / 20:39≈ on time ≈ +4 min
21:06 / 21:08≈ on time ≈ +6 min
21:28 / 21:30≈ on time ≈ +6 min
21:47≈ on time ≈ +6 min
22:00 / 22:01≈ on time ≈ +7 min
22:16 / 22:17≈ on time ≈ +7 min
22:33on time +7 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:43+3 min+7 min
Thu 5 Nov— 22:370 min—
Wed 4 Nov— 21:44+33 min+33 min
Tue 3 Nov— 22:54No data—
Mon 2 Nov— 22:340 min—
Sun 1 NovAmsterdam Sloterdijk 20:190 min—
Sat 31 OctSittard 22:340 min—
Fri 30 Oct— 22:34No data—
Thu 29 Oct— 19:360 min—
Wed 28 Oct— 22:350 min—
Tue 27 Oct— 22:39No data—
Mon 26 OctZaandam 22:49No data—
Sun 25 OctAmsterdam Sloterdijk 20:18No data—
Fri 23 Oct— 22:310 min+2 min
Thu 22 Oct— 22:550 min—
Wed 21 Oct— 22:34No data—
Tue 20 Oct— 21:560 min—
Mon 19 Oct— 22:35No data—
Sun 18 OctAmsterdam Sloterdijk 20:18+2 min+2 min
Sat 17 OctSittard 22:35Partial coverage0 min—
Fri 16 OctHoorn 22:55+11 min+11 min
Thu 15 Oct— 22:370 min—
Wed 14 OctHoorn 22:34No data—
Tue 13 Oct— 22:35No data—
Mon 12 Oct— 22:45+7 min+7 min
Sun 11 OctAmsterdam Sloterdijk 20:19+2 min+2 min
Sat 10 OctRoermond 22:350 min—
Fri 9 Oct— 22:48+7 min+8 min
Thu 8 Oct— 22:340 min+2 min
Wed 7 Oct— 22:340 min—