Train NS 4864 Hoorn – Amsterdam Centraal

Hoorn 19:06 → Amsterdam Centraal 20:35 Daily 1 h 29 min · 19 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 20:47 +3 min

  1. Hoorn19:06
  2. Alkmaar Noord19:26
  3. Castricum19:44
  4. Beverwijk19:57
  5. Santpoort Zuid20:08
  6. Amsterdam Sloterdijk20:30
  7. Amsterdam Centraal20:35

Next service: tomorrow 19:06 from Hoorn · Mon 16 Nov

Next departure 19:06 tomorrow · Hoorn
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 21 full · 2 partial · 7 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 29 full · 2 partial · 31 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: +1 min

Last 30 days

Arrival delay at Amsterdam Centraal, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +5 min · last fix heading to — +5 min
  • Sat 14 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
19:06on time on time
19:14 / 19:15≈ on time ≈ on time
19:21≈ on time ≈ on time
19:26≈ on time ≈ on time
19:29 / 19:34≈ on time ≈ on time
19:39≈ on time ≈ +1 min
19:44≈ on time ≈ +1 min
19:49≈ on time ≈ +1 min
19:54≈ on time ≈ +1 min
19:57 / 19:58≈ on time ≈ +1 min
20:03≈ on time ≈ +1 min
20:05≈ on time ≈ +1 min
20:08≈ on time ≈ +1 min
20:11≈ on time ≈ +1 min
20:15 / 20:17≈ on time ≈ +1 min
20:20≈ on time ≈ +1 min
20:25≈ on time ≈ +1 min
20:30≈ on time ≈ +1 min
20:35on 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
Sun 15 NovAmsterdam Sloterdijk 20:47Partial coverage+3 min+3 min
Sat 14 NovAmsterdam Sloterdijk 20:47+3 min+3 min
Fri 13 Nov— 20:340 min—
Thu 12 Nov— 20:180 min—
Wed 11 Nov— 20:340 min—
Tue 10 Nov— 20:39+2 min+3 min
Mon 9 Nov— 20:37+1 min+1 min
Sun 8 NovAmsterdam Sloterdijk 20:440 min—
Sat 7 NovBloemendaal 20:390 min—
Fri 6 Nov— 19:57+1 min—
Thu 5 Nov— 19:580 min—
Wed 4 Nov— 19:58+1 min—
Tue 3 Nov— 20:040 min—
Mon 2 Nov— 19:580 min—
Sun 1 NovAmsterdam Sloterdijk 20:44+1 min+1 min
Sat 31 OctAmsterdam Sloterdijk 20:450 min—
Fri 30 Oct— 20:360 min—
Thu 29 Oct— 20:360 min—
Wed 28 Oct— 20:360 min—
Tue 27 Oct— 20:39No data—
Mon 26 OctUitgeest 20:38No data—
Sun 25 OctAmsterdam Sloterdijk 20:44No data—
Sat 24 OctAmsterdam Sloterdijk 20:45No data—
Fri 23 OctAlkmaar Noord 20:360 min—
Thu 22 Oct— 20:37No data—
Wed 21 Oct— 20:37No data—
Tue 20 Oct— 20:370 min—
Mon 19 Oct— 20:360 min—
Sun 18 OctAmsterdam Sloterdijk 20:44Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 20:44No data—