Train NS 4832 Hoorn – Beverwijk

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

✓ Today’s run finished

Today, last fix heading to Heemskerk at 12:07 No data

  1. Hoorn11:06
  2. Heerhugowaard11:21
  3. Alkmaar Noord11:26
  4. Heiloo11:37
  5. Castricum11:43
  6. Heemskerk11:52
  7. Beverwijk11:56

Next service: tomorrow 11:06 from Hoorn · Fri 6 Nov

Next departure 11:06 tomorrow · Hoorn
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 8 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 65 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 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

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

  • Early 0% · 0
  • On time 100% · 24
  • 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=4
  • 100% T n=4
  • 100% F n=2
  • 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, 24 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:06on time on time
11:14 / 11:15≈ on time ≈ on time
11:21≈ on time ≈ on time
11:26≈ on time ≈ on time
11:29 / 11:32≈ on time ≈ on time
11:37≈ on time ≈ +1 min
11:43≈ on time ≈ +1 min
11:48≈ on time ≈ +1 min
11:52≈ on time ≈ +1 min
11:56on 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 NovHeemskerk 12:07No data—
Wed 4 NovHeemskerk 12:07Partial coverage0 min—
Tue 3 NovHeemskerk 12:08Partial coverage0 min—
Mon 2 NovHeemskerk 12:07Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 12:450 min—
Sat 31 OctAmsterdam Sloterdijk 12:440 min—
Fri 30 OctAmsterdam Sloterdijk 12:45No data—
Thu 29 OctAmsterdam Sloterdijk 12:440 min—
Wed 28 OctAmsterdam Sloterdijk 12:440 min—
Tue 27 OctAmsterdam Sloterdijk 12:440 min—
Mon 26 OctAmsterdam Sloterdijk 12:44No data—
Sun 25 OctAmsterdam Sloterdijk 12:48No data—
Sat 24 OctAmsterdam Sloterdijk 12:440 min—
Fri 23 OctAmsterdam Sloterdijk 12:470 min—
Thu 22 OctAmsterdam Sloterdijk 12:450 min—
Wed 21 OctAmsterdam Sloterdijk 12:440 min—
Tue 20 OctAmsterdam Sloterdijk 12:440 min—
Mon 19 OctAmsterdam Sloterdijk 12:45No data—
Sun 18 OctAmsterdam Sloterdijk 12:45+2 min+2 min
Sat 17 OctAmsterdam Sloterdijk 12:44No data—
Fri 16 OctAmsterdam Sloterdijk 12:44No data—
Thu 15 OctAmsterdam Sloterdijk 12:440 min—
Wed 14 OctAmsterdam Sloterdijk 12:44No data—
Tue 13 OctAmsterdam Sloterdijk 12:460 min—
Mon 12 OctAmsterdam Sloterdijk 12:440 min—
Sun 11 OctAmsterdam Sloterdijk 12:440 min—
Sat 10 OctAmsterdam Sloterdijk 12:45+1 min—
Fri 9 OctAmsterdam Sloterdijk 12:46+2 min+2 min
Thu 8 OctAmsterdam Sloterdijk 12:450 min—
Wed 7 OctAmsterdam Sloterdijk 12:440 min—