Train NS 4807 Alkmaar – Hoorn

Alkmaar 06:01 → Hoorn 06:24 Mon, Tue, Wed, Thu, Fri 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Obdam at 06:29 +1 min

  1. Alkmaar06:01
  2. Alkmaar Noord06:04
  3. Heerhugowaard06:09
  4. Obdam06:14
  5. Hoorn06:24

Next service: tomorrow 06:01 from Alkmaar · Thu 19 Nov

Next departure 06:01 tomorrow · Alkmaar
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 14 full · 1 partial · 2 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 23 full · 1 partial · 33 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

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=4
  • 100% T n=6
  • 100% W n=6
  • 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 (5 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
06:01on time on time
06:04≈ on time ≈ on time
06:09≈ on time ≈ on time
06:14 / 06:15≈ on time ≈ +1 min
06:24+1 min +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
Wed 18 NovObdam 06:29Partial coverage+1 min—
Tue 17 NovObdam 06:29+1 min+1 min
Mon 16 NovObdam 06:29+2 min+2 min
Fri 6 NovObdam 06:29No data—
Thu 5 NovObdam 06:290 min—
Wed 4 NovObdam 06:290 min—
Tue 3 NovObdam 06:29+1 min—
Mon 2 NovObdam 06:29No data—
Fri 30 OctObdam 06:30+1 min+1 min
Thu 29 OctObdam 06:290 min—
Wed 28 OctObdam 06:30+1 min—
Tue 27 OctObdam 06:30+1 min+1 min
Mon 26 OctObdam 06:30+1 min+1 min
Fri 23 OctObdam 06:290 min—
Thu 22 OctObdam 06:290 min—
Wed 21 OctObdam 06:290 min—
Tue 20 OctObdam 06:30+1 min+1 min
Mon 19 OctObdam 06:290 min—
Thu 15 OctObdam 06:30+1 min+1 min
Wed 14 OctObdam 06:30+1 min—
Tue 13 OctObdam 06:290 min—
Mon 12 OctObdam 06:31+1 min+1 min
Fri 9 OctAlkmaar Noord 06:190 min—
Thu 8 OctAlkmaar Noord 06:20+2 min+2 min
Wed 7 OctAlkmaar Noord 06:180 min—
Tue 6 OctAlkmaar Noord 06:190 min—
Mon 5 OctAlkmaar Noord 06:19No data—
Fri 2 OctObdam 06:29No data—
Thu 1 OctObdam 06:29No data—
Wed 30 SeptObdam 06:30No data—