Train NS 4839 Beverwijk – Hoorn

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:32 from Beverwijk · Thu 5 Nov

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

  • Mon 5 Oct Max en route +8 min · last fix heading to Alkmaar Noord +7 min

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

On-time by weekday

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