Train NS 2985 Enkhuizen – Maastricht

Enkhuizen 21:39 → Maastricht 01:03 Daily 3 h 24 min · 16 stops NS (Nederlandse Spoorwegen)

Running now · updated 21:47

Heading to Maastricht 0 min

Estimated arrival at Maastricht 01:03

  1. Enkhuizen21:39
  2. Hoogkarspel21:51
  3. Hoorn22:03
  4. Amsterdam Amstel22:47
  5. 's-Hertogenbosch23:36
  6. Roermond00:30
  7. Maastricht01:03

Today it is running no worse than usual: typical arrival delay is 0 min; 93% of the last 27 runs arrived on time.

On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 2 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 32 full · 1 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 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

  • Fri 23 Oct Max en route +7 min · last fix heading to — +7 min
  • Thu 29 Oct Max en route +9 min · last fix heading to — +6 min

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 94% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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 10Today
21:39on time on time
21:43≈ on time ≈ on time
21:46 / 21:47≈ on time ≈ on time
21:51 / 21:52≈ on time ≈ on time
21:59≈ on time ≈ on time
22:03 / 22:04≈ on time ≈ on time
22:29 / 22:31≈ on time ≈ on time
22:37 / 22:39≈ on time ≈ on time
22:47≈ on time ≈ on time
23:06 / 23:09≈ on time ≈ on time
23:36 / 23:38≈ on time ≈ +1 min
23:58 / 00:00≈ on time ≈ +1 min
00:17≈ on time ≈ +1 min
00:30 / 00:31≈ on time ≈ +1 min
00:46 / 00:47≈ on time ≈ +1 min
01:03on 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
Mon 9 Nov— 21:440 min—
Sun 8 NovAmsterdam Sloterdijk 22:440 min—
Sat 7 NovAmsterdam Sloterdijk 22:440 min—
Fri 6 Nov— 01:040 min—
Thu 5 Nov— 01:04No data—
Wed 4 Nov— 23:590 min—
Tue 3 Nov— 01:080 min—
Mon 2 Nov— 01:040 min—
Sun 1 NovAmsterdam Amstel 23:13+1 min+1 min
Sat 31 OctUtrecht Centraal 23:230 min—
Fri 30 Oct— 01:060 min—
Thu 29 Oct— 01:17+6 min+9 min
Wed 28 Oct— 01:040 min—
Tue 27 Oct— 00:380 min—
Mon 26 Oct— 01:070 min—
Sun 25 OctSittard 01:11No data—
Fri 23 Oct— 01:15+7 min+7 min
Thu 22 Oct— 01:060 min—
Wed 21 Oct— 01:040 min—
Tue 20 Oct— 01:090 min—
Mon 19 Oct— 22:260 min—
Sun 18 OctSittard 01:05Partial coverage0 min—
Sat 17 OctUtrecht Centraal 01:070 min—
Fri 16 Oct— 01:040 min—
Thu 15 Oct— 00:140 min—
Wed 14 Oct— 01:040 min—
Tue 13 Oct— 01:050 min—
Mon 12 Oct— 01:040 min+1 min
Sun 11 OctEde-Wageningen 23:500 min—
Sat 10 OctHoorn 01:050 min+5 min