Train NS 4856 Hoorn – Beverwijk

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:06 from Hoorn · Thu 5 Nov

Next departure 17:06 today · Hoorn
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 67 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: 0 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

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 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 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
17:06on time on time
17:14 / 17:15≈ on time ≈ on time
17:21≈ on time ≈ +1 min
17:26≈ on time ≈ +1 min
17:29 / 17:32≈ on time ≈ +1 min
17:37≈ on time ≈ +1 min
17:43≈ on time ≈ +2 min
17:48≈ on time ≈ +2 min
17:52≈ on time ≈ +2 min
17: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
Wed 4 NovHeemskerk 18:04No data—
Tue 3 NovHeemskerk 18:04No data—
Mon 2 NovHeemskerk 18:04Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 18:440 min—
Sat 31 OctAmsterdam Sloterdijk 18:440 min—
Fri 30 OctAmsterdam Sloterdijk 18:440 min—
Thu 29 OctHeemskerk 18:37No data—
Wed 28 OctBloemendaal 18:38+2 min+2 min
Tue 27 OctDriehuis 18:37No data—
Mon 26 OctSantpoort Zuid 18:360 min—
Sun 25 OctAmsterdam Sloterdijk 18:44No data—
Sat 24 OctAmsterdam Sloterdijk 18:440 min—
Fri 23 OctAmsterdam Sloterdijk 18:440 min—
Thu 22 OctAmsterdam Sloterdijk 18:440 min—
Wed 21 OctAmsterdam Sloterdijk 18:44No data—
Tue 20 OctAmsterdam Sloterdijk 18:440 min—
Mon 19 OctAmsterdam Sloterdijk 18:440 min—
Sun 18 OctAmsterdam Sloterdijk 18:440 min—
Sat 17 OctAmsterdam Sloterdijk 18:44No data—
Fri 16 OctAmsterdam Sloterdijk 18:44No data—
Thu 15 OctAmsterdam Sloterdijk 18:440 min—
Wed 14 OctUitgeest 18:46No data—
Tue 13 OctAmsterdam Sloterdijk 18:51No data—
Mon 12 OctAmsterdam Sloterdijk 18:440 min—
Sun 11 OctAmsterdam Sloterdijk 18:46+2 min+2 min
Sat 10 OctAmsterdam Sloterdijk 18:510 min—
Fri 9 OctAmsterdam Sloterdijk 18:440 min—
Thu 8 OctDriehuis 18:350 min—
Wed 7 OctSantpoort Zuid 18:360 min—
Tue 6 OctDriehuis 18:41+3 min+4 min