Train NS 4876 Hoorn – Amsterdam Centraal

Hoorn 22:06 → Amsterdam Centraal 23:36 Daily 1 h 30 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 22:06 from Hoorn · Mon 9 Nov

Next departure 22:06 today · Hoorn
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 16 full · 1 partial · 11 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 22 full · 1 partial · 27 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
22:06on time on time
22:14 / 22:15≈ on time ≈ on time
22:21≈ on time ≈ on time
22:26≈ on time ≈ on time
22:29 / 22:34≈ on time ≈ on time
22:39≈ on time ≈ on time
22:45≈ on time ≈ on time
22:49 / 22:50≈ on time ≈ on time
22:54≈ on time ≈ on time
22:57 / 22:59≈ on time ≈ on time
23:04≈ on time ≈ on time
23:07≈ on time ≈ on time
23:10≈ on time ≈ +1 min
23:13≈ on time ≈ +1 min
23:17 / 23:18≈ on time ≈ +1 min
23:21≈ on time ≈ +1 min
23:26≈ on time ≈ +1 min
23:31≈ on time ≈ +1 min
23:36on 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 NovAmsterdam Sloterdijk 23:44Partial coverage0 min—
Sat 7 NovHaarlem Spaarnwoude 23:340 min—
Fri 6 Nov— 22:570 min—
Thu 5 Nov— 22:570 min—
Wed 4 Nov— 22:58+1 min—
Tue 3 Nov— 23:00No data—
Sun 1 NovAmsterdam Sloterdijk 23:440 min—
Sat 31 OctHaarlem Spaarnwoude 23:360 min—
Fri 30 Oct— 23:38No data—
Thu 29 Oct— 23:380 min—
Wed 28 Oct— 23:38No data—
Tue 27 Oct— 23:38No data—
Mon 26 Oct— 23:37No data—
Sun 25 OctAmsterdam Sloterdijk 23:46No data—
Sat 24 OctHeiloo 23:360 min—
Fri 23 Oct— 23:380 min—
Thu 22 Oct— 23:380 min—
Wed 21 Oct— 23:37No data—
Tue 20 Oct— 23:370 min—
Mon 19 Oct— 23:37No data—
Sun 18 OctAmsterdam Sloterdijk 23:450 min—
Sat 17 OctAmsterdam Sloterdijk 23:44No data—
Fri 16 Oct— 23:370 min—
Thu 15 Oct— 23:38No data—
Wed 14 Oct— 23:370 min—
Tue 13 Oct— 23:38No data—
Mon 12 Oct— 23:380 min—
Sun 11 OctAmsterdam Sloterdijk 23:45+1 min+1 min
Sat 10 Oct— 23:170 min—
Fri 9 Oct— 23:370 min—