Train NS 4865 Amsterdam Centraal – Hoorn

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 19:25 from Amsterdam Centraal · Mon 9 Nov

Next departure 19:25 today · Amsterdam Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 19 full · 1 partial · 7 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 25 full · 1 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

  • Early 0% · 0
  • On time 100% · 26
  • 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=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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:25on time on time
19:31≈ on time ≈ on time
19:36≈ on time ≈ on time
19:40≈ on time ≈ on time
19:44 / 19:45≈ on time ≈ on time
19:49≈ on time ≈ on time
19:52≈ on time ≈ on time
19:54≈ on time ≈ on time
19:57≈ on time ≈ on time
20:02≈ on time ≈ on time
20:05≈ on time ≈ on time
20:10 / 20:11≈ on time ≈ +1 min
20:15≈ on time ≈ +1 min
20:20≈ on time ≈ +1 min
20:26 / 20:31≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:39≈ on time ≈ +1 min
20:44 / 20:45≈ on time ≈ +1 min
20:54on time +1 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 8 NovObdam 20:59Partial coverage0 min—
Sat 7 NovObdam 20:59+2 min+3 min
Fri 6 Nov— 20:540 min—
Thu 5 Nov— 20:550 min—
Wed 4 Nov— 20:540 min—
Mon 2 Nov— 20:540 min—
Sun 1 NovSantpoort Zuid 20:08+1 min+1 min
Sat 31 OctSantpoort Zuid 20:08+1 min+1 min
Thu 29 Oct— 20:550 min—
Wed 28 Oct— 21:000 min—
Tue 27 Oct— 21:02No data—
Mon 26 OctHaarlem Spaarnwoude 20:55No data—
Sun 25 OctObdam 20:59No data—
Sat 24 OctObdam 20:590 min—
Fri 23 OctAmsterdam Centraal 20:55+1 min—
Thu 22 Oct— 21:12No data—
Wed 21 Oct— 21:040 min—
Tue 20 Oct— 20:580 min—
Mon 19 Oct— 20:56No data—
Sun 18 OctObdam 20:59+1 min—
Sat 17 OctObdam 21:000 min—
Fri 16 OctSantpoort Noord 20:11No data—
Thu 15 Oct— 20:580 min—
Wed 14 OctAmsterdam Centraal 20:550 min—
Tue 13 Oct— 20:56No data—
Mon 12 Oct— 20:560 min—
Sun 11 OctAlkmaar Noord 20:480 min—
Sat 10 OctAlkmaar Noord 20:49+1 min—
Fri 9 Oct— 20:440 min+1 min
Thu 8 Oct— 20:43+1 min+1 min