Train NS 4884 Hoorn – Alkmaar

Hoorn 00:06 → Alkmaar 00:29 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:29 0 min

  1. Hoorn00:06
  2. Obdam00:14
  3. Heerhugowaard00:21
  4. Alkmaar Noord00:26
  5. Alkmaar00:29

Next service: tomorrow 00:06 from Hoorn · Fri 20 Nov

Next departure 00:06 tomorrow · Hoorn
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 8 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 Alkmaar, 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

32 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 100% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=6
  • 100% T n=6
  • 100% F n=4
  • 100% S n=5
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 stops).

Last 90 days, 32 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
00:06on time on time
00:14 / 00:15≈ on time ≈ on time
00:21≈ on time ≈ on time
00:26≈ on time ≈ on time
00:29on 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
Thu 19 Nov— 00:290 min—
Wed 18 Nov— 00:280 min—
Tue 17 Nov— 01:190 min—
Sun 15 NovAlkmaar Noord 00:390 min—
Sun 8 NovAlkmaar Noord 01:190 min—
Sat 7 Nov— 00:290 min—
Fri 6 Nov— 00:290 min—
Thu 5 Nov— 00:290 min—
Wed 4 Nov— 00:290 min—
Sun 1 NovAlkmaar Noord 00:39No data—
Sat 31 Oct— 00:300 min—
Fri 30 Oct— 00:300 min—
Thu 29 Oct— 00:410 min—
Wed 28 Oct— 01:190 min—
Tue 27 OctAlkmaar Noord 01:200 min—
Sun 25 OctAlkmaar Noord 00:400 min—
Sat 24 Oct— 00:310 min—
Fri 23 Oct— 00:390 min—
Thu 22 Oct— 00:300 min—
Wed 21 Oct— 01:180 min—
Tue 20 Oct— 00:280 min—
Sun 18 OctAlkmaar Noord 00:400 min—
Sat 17 OctAlkmaar Noord 00:400 min—
Fri 16 Oct— 01:050 min—
Thu 15 Oct— 01:040 min—
Wed 14 Oct— 01:120 min—
Tue 13 Oct— 01:160 min—
Mon 12 OctAlkmaar Noord 00:400 min—
Sun 11 Oct— 00:310 min—
Sat 10 Oct— 00:300 min—