Train NS 2984 Maastricht – Hoorn

Maastricht 21:59 → Hoorn 00:55 Daily 2 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:59 from Maastricht · Thu 5 Nov

Next departure 21:59 today · Maastricht
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 26 full · 0 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 Hoorn, 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 +28 min · last fix heading to — +8 min
  • Fri 16 Oct Max en route +14 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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:59on time on time
22:16 / 22:17≈ on time ≈ on time
22:31 / 22:32≈ on time ≈ on time
22:46≈ on time ≈ on time
23:02 / 23:04≈ on time ≈ on time
23:23 / 23:24≈ on time ≈ on time
23:51 / 23:54≈ on time ≈ on time
00:12≈ on time ≈ on time
00:20 / 00:23≈ on time ≈ on time
00:29≈ on time ≈ on time
00:55on 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
Wed 4 Nov— 00:570 min—
Mon 2 Nov— 00:570 min—
Sun 1 NovAmsterdam Centraal 00:570 min—
Sat 31 OctEindhoven Centraal 01:350 min—
Wed 28 Oct— 01:010 min—
Tue 27 Oct— 00:580 min—
Mon 26 Oct— 01:000 min—
Sun 25 OctAmsterdam Centraal 00:590 min—
Fri 23 Oct— 23:27+8 min+28 min
Thu 22 Oct— 00:560 min—
Wed 21 Oct— 01:180 min—
Tue 20 Oct— 00:580 min—
Sun 18 OctAmsterdam Centraal 01:000 min—
Sat 17 OctBovenkarspel Flora 01:330 min—
Fri 16 Oct— 01:39+7 min+14 min
Thu 15 Oct— 01:050 min—
Wed 14 Oct— 00:560 min—
Tue 13 Oct— 00:580 min—
Mon 12 Oct— 01:040 min—
Sun 11 OctZaandam 00:570 min—
Sat 10 OctMaastricht 01:290 min—
Fri 9 Oct— 01:240 min—
Thu 8 Oct— 00:240 min—
Wed 7 Oct— 22:060 min—
Tue 6 Oct— 00:580 min—
Mon 5 OctAmsterdam Amstel 00:570 min—
Sun 4 OctAmsterdam Sloterdijk 00:44No data—
Sat 3 OctDuivendrecht 00:18No data—
Sun 27 SeptBovenkarspel Flora 01:34No data—
Sat 26 Sept's-Hertogenbosch 23:38No data—