Train NS 4809 Beverwijk – Hoorn

Beverwijk 06:02 → Hoorn 06:54 Mon, Tue, Wed, Thu, Fri 0 h 52 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Obdam at 07:09 0 min

  1. Beverwijk06:02
  2. Uitgeest06:10
  3. Castricum06:20
  4. Alkmaar06:30
  5. Alkmaar Noord06:34
  6. Obdam06:44
  7. Hoorn06:54

Next service: tomorrow 06:02 from Beverwijk · Fri 6 Nov

Next departure 06:02 tomorrow · Beverwijk
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 1 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 20 full · 2 partial · 41 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

Worst days

  • Wed 7 Oct Max en route +4 min · last fix heading to Alkmaar Noord +4 min

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 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 80% W n=5
  • 100% T n=5
  • 100% F n=3
  • — S n=0
  • — S n=0

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
06:02on time on time
06:06≈ on time ≈ on time
06:10 / 06:15≈ on time ≈ on time
06:20≈ on time ≈ on time
06:25≈ on time ≈ +1 min
06:30 / 06:31≈ on time ≈ +1 min
06:34≈ on time ≈ +1 min
06:39≈ on time ≈ +1 min
06:44 / 06:45≈ on time ≈ +1 min
06: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
Thu 5 NovObdam 07:09Partial coverage0 min—
Wed 4 NovObdam 06:590 min—
Tue 3 NovObdam 06:59Partial coverage+1 min—
Mon 2 NovObdam 06:590 min—
Fri 30 OctObdam 06:59No data—
Thu 29 OctObdam 06:590 min—
Wed 28 OctObdam 07:00+1 min+1 min
Tue 27 OctObdam 07:00+1 min+1 min
Mon 26 OctObdam 06:590 min—
Fri 23 OctObdam 06:590 min—
Thu 22 OctObdam 06:590 min—
Wed 21 OctObdam 06:590 min—
Tue 20 OctObdam 06:59+1 min—
Mon 19 OctObdam 06:590 min—
Fri 16 OctHeemskerk 06:23+2 min+2 min
Thu 15 OctObdam 06:590 min+3 min
Wed 14 OctObdam 06:590 min—
Tue 13 OctObdam 07:00+1 min—
Mon 12 OctObdam 06:590 min—
Fri 9 OctAlkmaar Noord 06:490 min—
Thu 8 OctAlkmaar Noord 06:490 min—
Wed 7 OctAlkmaar Noord 06:52+4 min+4 min
Tue 6 OctAlkmaar Noord 06:490 min+1 min
Mon 5 OctAlkmaar Noord 06:51No data—
Fri 2 OctHeiloo 07:02No data—
Thu 1 OctObdam 07:10No data—
Wed 30 SeptObdam 06:59No data—
Tue 29 SeptObdam 06:59No data—
Mon 28 SeptObdam 06:59No data—
Fri 25 SeptObdam 06:59No data—