Train NS 4877 Beverwijk – Hoorn

Beverwijk 23:02 → Hoorn 23:54 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 23:02 from Beverwijk · Thu 5 Nov

Next departure 23:02 today · Beverwijk
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 4 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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=3
  • 100% W n=5
  • 100% T n=3
  • 100% F n=3
  • 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, 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
23:02on time on time
23:06≈ on time ≈ on time
23:10 / 23:15≈ on time ≈ on time
23:20≈ on time ≈ on time
23:25≈ on time ≈ on time
23:30 / 23:31≈ on time ≈ on time
23:34≈ on time ≈ on time
23:39≈ on time ≈ on time
23:44 / 23:45≈ on time ≈ on time
23:54on time on time

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 Nov— 23:540 min—
Tue 3 Nov— 23:54No data—
Sun 1 NovSantpoort Zuid 23:08+2 min+2 min
Sat 31 OctSantpoort Zuid 23:060 min—
Thu 29 Oct— 23:560 min—
Wed 28 Oct— 23:560 min—
Tue 27 Oct— 23:560 min—
Mon 26 Oct— 00:000 min—
Sun 25 OctObdam 23:59No data—
Sat 24 OctAmsterdam Centraal 23:550 min—
Fri 23 Oct— 23:550 min—
Wed 21 Oct— 23:550 min—
Tue 20 Oct— 23:550 min—
Mon 19 Oct— 00:030 min+8 min
Sun 18 OctObdam 23:590 min—
Sat 17 OctObdam 23:59No data—
Fri 16 Oct— 23:110 min—
Thu 15 Oct— 23:570 min—
Wed 14 Oct— 23:550 min—
Tue 13 Oct— 23:56No data—
Mon 12 Oct— 22:450 min—
Sun 11 OctAlkmaar Noord 23:490 min—
Sat 10 Oct— 23:420 min—
Fri 9 Oct— 23:410 min—
Thu 8 Oct— 23:42+1 min—
Wed 7 Oct— 23:410 min—
Tue 6 Oct— 23:410 min—
Mon 5 Oct— 23:410 min—
Sun 4 OctHeemskerk 23:20No data—
Sat 3 OctHeemskerk 23:15No data—