Train NS 4856 Hoorn – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 18:44 No data

  1. Hoorn17:06
  2. Alkmaar Noord17:26
  3. Castricum17:44
  4. Beverwijk17:57
  5. Santpoort Zuid18:08
  6. Amsterdam Sloterdijk18:30
  7. Amsterdam Centraal18:35

Next service: tomorrow 17:06 from Hoorn · Mon 26 Oct

Full trip card
Next departure 17:06 tomorrow · Hoorn
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 15 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 74 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 Amsterdam Centraal, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=1
  • 100% T n=3
  • 100% F n=2
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

StopSched.
Hoorn
17:06
Obdam
17:14 / 17:15
Heerhugowaard
17:21
Alkmaar Noord
17:26
Alkmaar
17:29 / 17:34
Heiloo
17:39
Castricum
17:44
Uitgeest
17:49
Heemskerk
17:54
Beverwijk
17:57 / 17:58
Driehuis
18:03
Santpoort Noord
18:05
Santpoort Zuid
18:08
Bloemendaal
18:11
Haarlem
18:15 / 18:17
Haarlem Spaarnwoude
18:20
Halfweg-Zwanenburg
18:25
Amsterdam Sloterdijk
18:30
Amsterdam Centraal
18:35

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.

Recent runs

DateLast stopFinalMax
Sun 25 OctAmsterdam Sloterdijk 18:44No data—
Sat 24 OctAmsterdam Sloterdijk 18:44Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 18:440 min—
Thu 22 OctAmsterdam Sloterdijk 18:44Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 18:44No data—
Tue 20 OctAmsterdam Sloterdijk 18:440 min—
Mon 19 OctAmsterdam Sloterdijk 18:44Partial coverage0 min—
Sun 18 OctAmsterdam Sloterdijk 18:440 min—
Sat 17 OctAmsterdam Sloterdijk 18:44No data—
Fri 16 OctAmsterdam Sloterdijk 18:44No data—
Thu 15 OctAmsterdam Sloterdijk 18:440 min—
Wed 14 OctUitgeest 18:46No data—
Tue 13 OctAmsterdam Sloterdijk 18:51No data—
Mon 12 OctAmsterdam Sloterdijk 18:440 min—
Sun 11 OctAmsterdam Sloterdijk 18:46+2 min+2 min
Sat 10 OctAmsterdam Sloterdijk 18:510 min—
Fri 9 OctAmsterdam Sloterdijk 18:440 min—
Thu 8 OctDriehuis 18:350 min—
Wed 7 OctSantpoort Zuid 18:360 min—
Tue 6 OctDriehuis 18:41+3 min+4 min
Mon 5 OctBloemendaal 18:35+1 min+1 min
Sun 4 OctBloemendaal 18:26No data—
Sat 3 OctBloemendaal 18:29No data—
Fri 2 OctAmsterdam Sloterdijk 18:44No data—
Thu 1 OctSantpoort Noord 18:19No data—
Wed 30 SeptSantpoort Zuid 18:18No data—
Tue 29 SeptSantpoort Noord 18:19No data—
Mon 28 SeptSantpoort Noord 18:19No data—
Sun 27 SeptAmsterdam Sloterdijk 18:45No data—
Sat 26 SeptAmsterdam Sloterdijk 18:45No data—