Train NS 4831 Beverwijk – Hoorn

Beverwijk 11:32 → Hoorn 12:24 Daily 0 h 52 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 11:32 from Beverwijk · Sat 7 Nov

Next departure 11:32 today · Beverwijk
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%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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=2
  • 100% T n=3
  • 100% W n=4
  • 100% T n=3
  • 100% F n=4
  • 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
11:32on time on time
11:36≈ on time ≈ on time
11:40 / 11:41≈ on time ≈ on time
11:45≈ on time ≈ on time
11:51≈ on time ≈ on time
11:56 / 12:01≈ on time ≈ on time
12:04≈ on time ≈ on time
12:09≈ on time ≈ on time
12:14 / 12:15≈ on time ≈ on time
12:24on time on time

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
Fri 6 NovObdam 12:29No data—
Thu 5 NovObdam 12:29No data—
Wed 4 NovObdam 12:29Partial coverage0 min—
Tue 3 NovObdam 12:29No data—
Mon 2 NovObdam 12:29No data—
Sun 1 NovSantpoort Zuid 11:370 min—
Sat 31 OctSantpoort Zuid 11:370 min—
Fri 30 OctObdam 12:300 min—
Thu 29 OctObdam 12:320 min—
Wed 28 OctObdam 12:290 min—
Tue 27 OctObdam 12:290 min—
Mon 26 OctObdam 12:400 min—
Sun 25 OctObdam 12:30No data—
Sat 24 OctObdam 12:290 min—
Fri 23 OctObdam 12:290 min—
Thu 22 OctHeiloo 12:380 min—
Wed 21 OctObdam 12:290 min—
Tue 20 OctObdam 12:290 min—
Mon 19 OctObdam 12:290 min—
Sun 18 OctObdam 12:290 min—
Sat 17 OctObdam 12:29No data—
Fri 16 OctHeemskerk 11:500 min—
Thu 15 OctObdam 12:29No data—
Wed 14 OctObdam 12:29No data—
Tue 13 OctObdam 12:29No data—
Mon 12 OctObdam 12:29No data—
Sun 11 OctAlkmaar Noord 12:20+1 min+2 min
Sat 10 OctAlkmaar Noord 12:180 min—
Fri 9 OctAlkmaar Noord 12:180 min—
Thu 8 OctAlkmaar Noord 12:190 min—