Train NS 4860 Hoorn – Beverwijk

Hoorn 18:06 → Beverwijk 18:56 Daily 0 h 50 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 18:06 from Hoorn · Fri 6 Nov

Next departure 18:06 today · Hoorn
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 17 full · 2 partial · 10 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Mon 2 Nov Max en route +4 min · last fix heading to Hoorn +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Halfweg-Zwanenburg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 100% W n=1
  • 100% T n=4
  • 50% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
18:06on time on time
18:14 / 18:15≈ on time ≈ on time
18:21≈ on time ≈ +1 min
18:26≈ on time ≈ +1 min
18:29 / 18:30≈ on time ≈ +1 min
18:35≈ on time ≈ +1 min
18:40≈ on time ≈ +2 min
18:44 / 18:48≈ on time ≈ +2 min
18:52≈ on time ≈ +2 min
18:56on time +2 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
Thu 5 NovHoorn 18:57Partial coverage0 min—
Wed 4 NovObdam 18:59No data—
Tue 3 NovHoorn 18:58Partial coverage0 min—
Mon 2 NovHoorn 18:59+4 min+4 min
Sun 1 NovAmsterdam Sloterdijk 19:440 min—
Sat 31 OctAmsterdam Sloterdijk 19:440 min—
Fri 30 OctHeemskerk 19:36No data—
Thu 29 Oct— 19:38+2 min+2 min
Wed 28 OctHoorn 19:360 min—
Tue 27 Oct— 19:370 min—
Mon 26 OctHoorn 19:380 min—
Sun 25 OctAmsterdam Sloterdijk 19:44No data—
Sat 24 OctAmsterdam Sloterdijk 19:44No data—
Fri 23 OctHalfweg-Zwanenburg 19:39+3 min+3 min
Thu 22 OctCastricum 19:39No data—
Wed 21 OctCastricum 19:37No data—
Tue 20 OctCastricum 19:36No data—
Mon 19 OctCastricum 19:360 min—
Sun 18 OctAmsterdam Sloterdijk 19:440 min—
Sat 17 OctAmsterdam Sloterdijk 19:44No data—
Fri 16 OctAmsterdam Sloterdijk 19:44No data—
Thu 15 OctAlkmaar Noord 19:390 min—
Wed 14 OctAmsterdam Sloterdijk 19:42No data—
Tue 13 OctHeiloo 19:370 min—
Mon 12 OctCastricum 19:360 min—
Sun 11 OctAmsterdam Sloterdijk 19:440 min—
Sat 10 OctAmsterdam Sloterdijk 19:440 min—
Fri 9 OctHeiloo 19:380 min—
Thu 8 Oct— 19:360 min—
Tue 6 Oct— 19:360 min—