Train NS 4862 Hoorn – Beverwijk

Hoorn 18:36 → Beverwijk 19:26 Daily 0 h 50 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 19:28 No data

  1. Hoorn18:36
  2. Heerhugowaard18:51
  3. Alkmaar Noord18:56
  4. Heiloo19:08
  5. Castricum19:13
  6. Heemskerk19:23
  7. Beverwijk19:26

Next service: tomorrow 18:36 from Hoorn · Fri 6 Nov

Next departure 18:36 tomorrow · Hoorn
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 10 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Beverwijk, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 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=3
  • 100% W n=3
  • 100% T n=4
  • 67% F n=3
  • 100% S n=2
  • 100% S n=3

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
18:36on time on time
18:44 / 18:45≈ on time ≈ on time
18:51≈ on time ≈ +1 min
18:56≈ on time ≈ +1 min
18:59 / 19:03≈ on time ≈ +1 min
19:08≈ on time ≈ +1 min
19:13≈ on time ≈ +1 min
19:18≈ on time ≈ +2 min
19:23≈ on time ≈ +2 min
19:26on time +2 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 Nov— 19:28No data—
Wed 4 Nov— 19:29No data—
Tue 3 Nov— 19:27No data—
Mon 2 Nov— 19:270 min—
Sun 1 NovAmsterdam Sloterdijk 20:140 min—
Sat 31 OctAmsterdam Sloterdijk 20:17+2 min+2 min
Fri 30 OctHoorn 20:070 min—
Thu 29 Oct— 20:070 min—
Wed 28 Oct— 20:070 min—
Tue 27 Oct— 20:08No data—
Mon 26 OctHaarlem 20:07No data—
Sun 25 OctAmsterdam Sloterdijk 20:16No data—
Sat 24 OctAmsterdam Sloterdijk 20:18No data—
Fri 23 OctHeemskerk 20:09+2 min+2 min
Thu 22 OctObdam 20:290 min—
Wed 21 OctHoorn 20:080 min—
Tue 20 OctHoorn 20:080 min—
Mon 19 OctHoorn 20:080 min—
Sun 18 OctAmsterdam Sloterdijk 20:150 min—
Sat 17 OctAmsterdam Sloterdijk 20:15No data—
Fri 16 OctHaarlem Spaarnwoude 20:08No data—
Thu 15 Oct— 20:070 min—
Wed 14 OctHaarlem 20:07No data—
Tue 13 OctHoorn 20:080 min—
Mon 12 OctHoorn 20:180 min—
Sun 11 OctAmsterdam Sloterdijk 20:150 min—
Sat 10 OctAmsterdam Sloterdijk 20:16+1 min+1 min
Fri 9 Oct— 20:12+5 min+5 min
Thu 8 Oct— 20:08+2 min+3 min
Wed 7 Oct— 20:070 min—