Train NS 4819 Beverwijk – Hoorn

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

✓ Today’s run finished

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

  1. Beverwijk08:32
  2. Uitgeest08:40
  3. Castricum08:45
  4. Alkmaar08:56
  5. Alkmaar Noord09:04
  6. Obdam09:14
  7. Hoorn09:24

Next service: tomorrow 08:32 from Beverwijk · Fri 6 Nov

Next departure 08:32 tomorrow · Beverwijk
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 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 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

  • Sat 24 Oct Max en route +7 min · last fix heading to Obdam +6 min

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 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=4
  • 100% F n=4
  • 75% 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, 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
08:32on time on time
08:36≈ on time ≈ on time
08:40 / 08:41≈ on time ≈ on time
08:45≈ on time ≈ on time
08:51≈ on time ≈ on time
08:56 / 09:01≈ on time ≈ on time
09:04≈ on time ≈ +1 min
09:09≈ on time ≈ +1 min
09:14 / 09:15≈ on time ≈ +1 min
09: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
Thu 5 NovObdam 09:29No data—
Wed 4 NovObdam 09:29Partial coverage+1 min—
Tue 3 NovObdam 09:29No data—
Mon 2 NovObdam 09:29No data—
Sun 1 NovSantpoort Zuid 08:370 min—
Sat 31 OctSantpoort Zuid 08:370 min—
Fri 30 OctObdam 09:290 min—
Thu 29 OctObdam 09:320 min—
Wed 28 OctObdam 09:290 min—
Tue 27 OctObdam 09:29No data—
Mon 26 OctObdam 09:300 min—
Sun 25 OctObdam 09:30No data—
Sat 24 OctObdam 09:35+6 min+7 min
Fri 23 OctObdam 09:290 min—
Thu 22 OctObdam 09:290 min—
Wed 21 OctObdam 09:29No data—
Tue 20 OctObdam 09:290 min—
Mon 19 OctObdam 09:290 min—
Sun 18 OctObdam 09:30+1 min+2 min
Sat 17 OctObdam 09:290 min—
Fri 16 OctHeemskerk 08:490 min—
Thu 15 OctObdam 09:290 min—
Wed 14 OctObdam 09:29No data—
Tue 13 OctObdam 09:310 min—
Mon 12 OctObdam 09:310 min—
Sun 11 OctAlkmaar Noord 09:22+3 min+8 min
Sat 10 OctAlkmaar Noord 09:200 min+1 min
Fri 9 OctAlkmaar Noord 09:190 min—
Thu 8 OctAlkmaar Noord 09:190 min—
Wed 7 OctAlkmaar Noord 09:180 min—