Train NS 4833 Beverwijk – Hoorn

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 12:02 today · Beverwijk
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 9 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 20 full · 2 partial · 66 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

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

  • Early 0% · 0
  • On time 100% · 22
  • 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=4
  • 100% W n=3
  • 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, 22 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
12:02on time on time
12:06≈ on time ≈ on time
12:10 / 12:11≈ on time ≈ on time
12:16≈ on time ≈ on time
12:21≈ on time ≈ on time
12:26 / 12:31≈ on time ≈ +1 min
12:34≈ on time ≈ +1 min
12:39≈ on time ≈ +1 min
12:44 / 12:45≈ on time ≈ +1 min
12: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 NovObdam 12:59Partial coverage0 min—
Tue 3 NovObdam 12:59No data—
Mon 2 NovObdam 12:59Partial coverage0 min—
Sun 1 NovSantpoort Zuid 12:08+1 min—
Sat 31 OctSantpoort Zuid 12:08+1 min+2 min
Fri 30 OctObdam 12:590 min—
Thu 29 OctObdam 12:590 min—
Wed 28 OctObdam 12:590 min—
Tue 27 OctObdam 12:590 min—
Mon 26 OctObdam 13:00No data—
Sun 25 OctObdam 12:59No data—
Sat 24 OctObdam 12:590 min—
Fri 23 OctObdam 12:590 min—
Thu 22 OctObdam 12:590 min—
Wed 21 OctObdam 13:04No data—
Tue 20 OctObdam 13:060 min—
Mon 19 OctObdam 12:59No data—
Sun 18 OctObdam 13:00+1 min—
Sat 17 OctObdam 12:59No data—
Fri 16 OctHeemskerk 12:21No data—
Thu 15 OctObdam 12:59No data—
Wed 14 OctObdam 12:59No data—
Tue 13 OctObdam 12:590 min—
Mon 12 OctObdam 12:590 min—
Sun 11 OctAlkmaar Noord 12:480 min—
Sat 10 OctAlkmaar Noord 12:480 min—
Fri 9 OctAlkmaar Noord 12:490 min—
Thu 8 OctAlkmaar Noord 12:480 min—
Wed 7 OctAlkmaar Noord 12:52+3 min+4 min
Tue 6 OctAlkmaar Noord 12:49+1 min—