Train NS 4866 Hoorn – Amsterdam Centraal

Hoorn 19:36 → Amsterdam Centraal 21:05 Daily 1 h 29 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 19:36 from Hoorn · Fri 20 Nov

Next departure 19:36 today · Hoorn
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 7 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 26 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: 0 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

  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 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 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 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:36on time on time
19:44 / 19:45≈ on time ≈ on time
19:51≈ on time ≈ on time
19:56≈ on time ≈ on time
19:59 / 20:00≈ on time ≈ on time
20:05≈ on time ≈ on time
20:10≈ on time ≈ on time
20:15 / 20:20≈ on time ≈ on time
20:24≈ on time ≈ on time
20:27 / 20:28≈ on time ≈ +1 min
20:33≈ on time ≈ +1 min
20:36≈ on time ≈ +1 min
20:39≈ on time ≈ +1 min
20:42≈ on time ≈ +1 min
20:46 / 20:47≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
20:55≈ on time ≈ +1 min
21:00≈ on time ≈ +1 min
21:05on 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
Thu 19 Nov— 20:490 min—
Wed 18 Nov— 20:190 min—
Tue 17 Nov— 21:040 min+2 min
Mon 16 Nov— 21:040 min—
Sun 15 NovAmsterdam Sloterdijk 21:140 min—
Sat 14 NovAmsterdam Sloterdijk 21:140 min—
Fri 13 Nov— 21:040 min—
Thu 12 Nov— 20:520 min—
Wed 11 Nov— 21:040 min—
Tue 10 Nov— 21:040 min—
Mon 9 Nov— 21:040 min—
Sun 8 NovAmsterdam Sloterdijk 21:140 min+1 min
Sat 7 NovAmsterdam Sloterdijk 21:140 min—
Fri 6 Nov— 20:270 min—
Thu 5 Nov— 20:28No data—
Wed 4 Nov— 20:280 min—
Mon 2 Nov— 20:27No data—
Sun 1 NovAmsterdam Sloterdijk 21:140 min—
Sat 31 OctAmsterdam Sloterdijk 21:150 min—
Thu 29 Oct— 21:060 min—
Wed 28 Oct— 21:06No data—
Tue 27 Oct— 21:07No data—
Mon 26 OctHeerhugowaard 21:06No data—
Sun 25 OctAmsterdam Sloterdijk 21:15No data—
Sat 24 OctAmsterdam Sloterdijk 21:150 min—
Fri 23 Oct— 21:07+1 min—
Thu 22 Oct— 21:07No data—
Wed 21 Oct— 21:070 min—
Tue 20 Oct— 21:08No data—
Mon 19 Oct— 21:07No data—