Train NS 4857 Beverwijk – Hoorn

Beverwijk 18:02 → Hoorn 18:54 Daily 0 h 52 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:02 from Beverwijk · Thu 5 Nov

Next departure 18:02 today · Beverwijk
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 8 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 21 full · 2 partial · 65 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 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

  • Sun 1 Nov Max en route +3 min · last fix heading to Santpoort Zuid +3 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 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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
18:02on time on time
18:06≈ on time ≈ on time
18:10 / 18:11≈ on time ≈ on time
18:16≈ on time ≈ on time
18:21≈ on time ≈ on time
18:26 / 18:31≈ on time ≈ on time
18:34≈ on time ≈ +1 min
18:39≈ on time ≈ +1 min
18:44 / 18:45≈ on time ≈ +1 min
18:54on 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
Wed 4 NovUitgeest 18:59No data—
Tue 3 NovUitgeest 18:54Partial coverage0 min—
Mon 2 NovHeemskerk 18:54Partial coverage+2 min+2 min
Sun 1 NovSantpoort Zuid 18:10+3 min+3 min
Sat 31 OctSantpoort Zuid 18:07+1 min+1 min
Fri 30 OctObdam 18:59No data—
Thu 29 OctAmsterdam Centraal 18:58+2 min+2 min
Wed 28 OctUitgeest 18:550 min—
Tue 27 OctAmsterdam Centraal 19:00No data—
Mon 26 OctHeemskerk 18:570 min—
Sun 25 OctObdam 18:59No data—
Sat 24 OctObdam 18:590 min—
Fri 23 OctObdam 18:59+1 min—
Thu 22 OctObdam 18:59No data—
Wed 21 OctHeerhugowaard 18:560 min—
Tue 20 OctAmsterdam Centraal 18:580 min—
Mon 19 OctHeerhugowaard 19:000 min—
Sun 18 OctObdam 19:000 min+1 min
Sat 17 OctObdam 18:59No data—
Fri 16 OctHeemskerk 18:23No data—
Thu 15 OctHeiloo 18:58No data—
Wed 14 OctObdam 18:590 min—
Tue 13 OctHeerhugowaard 19:300 min—
Mon 12 OctObdam 18:590 min—
Sun 11 OctAlkmaar Noord 18:490 min—
Sat 10 OctAlkmaar Noord 18:490 min—
Fri 9 OctAlkmaar Noord 18:480 min—
Thu 8 OctBeverwijk 18:420 min—
Wed 7 OctSantpoort Noord 18:410 min—
Tue 6 OctBeverwijk 18:410 min—