Train NS 4815 Beverwijk – Hoorn

Beverwijk 07:32 → Hoorn 08:24 Mon, Tue, Wed, Thu, Fri, Sat 0 h 52 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 07:32 from Beverwijk · Fri 6 Nov

Next departure 07:32 today · Beverwijk
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 23 full · 1 partial · 1 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 25 full · 1 partial · 49 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: +1 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

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

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 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
07:32on time on time
07:36≈ on time ≈ on time
07:40 / 07:41≈ on time ≈ on time
07:45≈ on time ≈ on time
07:51≈ on time ≈ on time
07:56 / 08:01≈ on time ≈ on time
08:04≈ on time ≈ on time
08:09≈ on time ≈ +1 min
08:14 / 08:15≈ on time ≈ +1 min
08:24on 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
Thu 5 NovObdam 08:29Partial coverage0 min—
Wed 4 NovObdam 08:290 min—
Tue 3 NovObdam 08:290 min—
Mon 2 NovObdam 08:29No data—
Sat 31 OctSantpoort Zuid 07:370 min—
Fri 30 OctObdam 08:290 min—
Thu 29 OctObdam 08:300 min—
Wed 28 OctObdam 08:300 min—
Tue 27 OctObdam 08:290 min—
Mon 26 OctObdam 08:290 min—
Sat 24 OctObdam 08:30+1 min+1 min
Fri 23 OctObdam 08:290 min—
Thu 22 OctObdam 08:310 min—
Wed 21 OctObdam 08:300 min—
Tue 20 OctObdam 08:290 min—
Mon 19 OctObdam 08:290 min—
Sat 17 OctObdam 08:290 min—
Fri 16 OctHeemskerk 07:510 min—
Thu 15 OctObdam 08:300 min—
Wed 14 OctObdam 08:290 min—
Tue 13 OctObdam 08:290 min—
Mon 12 OctObdam 08:290 min—
Sat 10 OctAlkmaar Noord 08:180 min—
Fri 9 OctAlkmaar Noord 08:21+2 min+3 min
Thu 8 OctAlkmaar Noord 08:19+1 min—
Wed 7 OctAlkmaar Noord 08:180 min—
Tue 6 OctAlkmaar Noord 08:21+1 min+2 min
Mon 5 OctAlkmaar Noord 08:20No data—
Sat 3 OctHeemskerk 07:49No data—
Fri 2 OctObdam 08:29No data—