Train NS 4823 Beverwijk – Hoorn

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

✓ Today’s run finished

Today, last fix heading to Obdam at 10:29 No data

  1. Beverwijk09:32
  2. Uitgeest09:40
  3. Castricum09:45
  4. Alkmaar09:56
  5. Alkmaar Noord10:04
  6. Obdam10:14
  7. Hoorn10:24

Next service: tomorrow 09:32 from Beverwijk · Sat 7 Nov

Next departure 09:32 tomorrow · Beverwijk
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 17 full · 1 partial · 12 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 19 full · 1 partial · 69 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=2
  • 100% W n=5
  • 100% T n=3
  • 100% F n=1
  • 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, 20 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:32on time on time
09:36≈ on time ≈ on time
09:40 / 09:41≈ on time ≈ on time
09:45≈ on time ≈ on time
09:51≈ on time ≈ on time
09:56 / 10:01≈ on time ≈ on time
10:04≈ on time ≈ on time
10:09≈ on time ≈ on time
10:14 / 10:15≈ on time ≈ on time
10: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
Fri 6 NovObdam 10:29No data—
Thu 5 NovObdam 10:29No data—
Wed 4 NovObdam 10:29Partial coverage0 min—
Tue 3 NovObdam 10:29No data—
Mon 2 NovObdam 10:29No data—
Sun 1 NovSantpoort Zuid 09:38+1 min—
Sat 31 OctSantpoort Zuid 09:360 min+1 min
Fri 30 OctObdam 10:29No data—
Thu 29 OctHeiloo 11:500 min—
Wed 28 OctObdam 10:300 min—
Tue 27 OctObdam 10:290 min—
Mon 26 OctObdam 10:30No data—
Sun 25 OctObdam 10:29No data—
Sat 24 OctObdam 10:290 min—
Fri 23 OctObdam 10:29No data—
Thu 22 OctObdam 10:29No data—
Wed 21 OctObdam 10:300 min—
Tue 20 OctObdam 10:29No data—
Mon 19 OctObdam 10:330 min—
Sun 18 OctObdam 10:29+1 min—
Sat 17 OctObdam 10:30+1 min—
Fri 16 OctHeemskerk 09:50No data—
Thu 15 OctDriehuis 10:580 min—
Wed 14 OctObdam 10:290 min—
Tue 13 OctObdam 10:29No data—
Mon 12 OctObdam 10:290 min—
Sun 11 OctAlkmaar Noord 10:200 min+1 min
Sat 10 OctAlkmaar Noord 10:19+1 min—
Fri 9 OctAlkmaar Noord 10:190 min—
Thu 8 OctAlkmaar Noord 10:190 min—