Train NS 4826 Hoorn – Beverwijk

Hoorn 09:36 → Beverwijk 10:26 Daily 0 h 50 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 09:36 from Hoorn · Sat 7 Nov

Next departure 09:36 today · Hoorn
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 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

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=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • 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
09:36on time on time
09:44 / 09:45≈ on time ≈ on time
09:51≈ on time ≈ on time
09:56≈ on time ≈ on time
09:59 / 10:03≈ on time ≈ on time
10:08≈ on time ≈ on time
10:13≈ on time ≈ on time
10:18≈ on time ≈ on time
10:23≈ on time ≈ on time
10:26on 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 NovHeemskerk 10:38No data—
Thu 5 NovHeemskerk 10:38No data—
Wed 4 NovHeemskerk 10:37Partial coverage0 min—
Tue 3 NovHeemskerk 10:38No data—
Mon 2 NovHeemskerk 10:37No data—
Sun 1 NovAmsterdam Sloterdijk 11:150 min—
Sat 31 OctAmsterdam Sloterdijk 11:16+1 min+1 min
Fri 30 OctAmsterdam Sloterdijk 11:150 min—
Thu 29 OctAmsterdam Sloterdijk 11:170 min—
Wed 28 OctAmsterdam Sloterdijk 11:150 min—
Tue 27 OctAmsterdam Sloterdijk 11:150 min—
Mon 26 OctAmsterdam Sloterdijk 11:150 min—
Sun 25 OctAmsterdam Sloterdijk 11:15No data—
Sat 24 OctAmsterdam Sloterdijk 11:16+1 min+2 min
Fri 23 OctAmsterdam Sloterdijk 11:150 min—
Thu 22 OctAmsterdam Sloterdijk 11:150 min—
Wed 21 OctAmsterdam Sloterdijk 11:17No data—
Tue 20 OctAmsterdam Sloterdijk 11:190 min—
Mon 19 OctAmsterdam Sloterdijk 11:160 min—
Sun 18 OctAmsterdam Sloterdijk 11:150 min—
Sat 17 OctAmsterdam Sloterdijk 11:150 min—
Fri 16 OctAmsterdam Sloterdijk 11:17No data—
Thu 15 OctAmsterdam Sloterdijk 11:17No data—
Wed 14 OctAmsterdam Sloterdijk 11:160 min—
Tue 13 OctAmsterdam Sloterdijk 11:160 min—
Mon 12 OctAmsterdam Sloterdijk 11:17No data—
Sun 11 OctAmsterdam Sloterdijk 11:150 min—
Sat 10 OctAmsterdam Sloterdijk 11:150 min—
Fri 9 OctAmsterdam Sloterdijk 11:16No data—
Thu 8 OctAmsterdam Sloterdijk 11:150 min—