Train NS 4811 Amsterdam Centraal – Hoorn

Amsterdam Centraal 05:55 → Hoorn 07:24 Mon, Tue, Wed, Thu, Fri, Sat 1 h 29 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +2 min

Next service: today 05:55 from Amsterdam Centraal · Tue 17 Nov

Next departure 05:55 today · Amsterdam Centraal
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 3 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 32 full · 1 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Fri 23 Oct Max en route +4 min · last fix heading to Obdam +4 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Obdam +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=6
  • 80% T n=5
  • 80% F n=5
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
05:55on time on time
06:01≈ on time ≈ on time
06:06≈ on time ≈ on time
06:10≈ on time ≈ on time
06:14 / 06:15≈ on time ≈ +1 min
06:19≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:24≈ on time ≈ +1 min
06:27≈ on time ≈ +1 min
06:32≈ on time ≈ +1 min
06:36≈ on time ≈ +1 min
06:40 / 06:41≈ on time ≈ +1 min
06:45≈ on time ≈ +1 min
06:51≈ on time ≈ +1 min
06:56 / 07:01≈ on time ≈ +1 min
07:04≈ on time ≈ +2 min
07:09≈ on time ≈ +2 min
07:14 / 07:15≈ on time ≈ +2 min
07:24on 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
Mon 16 NovObdam 07:29Partial coverage+2 min+2 min
Sat 14 NovObdam 07:29+1 min—
Fri 13 NovHeiloo 07:09+3 min+3 min
Thu 12 NovHeiloo 07:040 min—
Wed 11 NovHeiloo 07:04+2 min+2 min
Tue 10 NovHeiloo 07:040 min—
Mon 9 NovHeiloo 07:04+1 min—
Sat 7 NovObdam 07:290 min—
Fri 6 NovObdam 07:34No data—
Thu 5 NovObdam 07:29No data—
Wed 4 NovObdam 07:290 min—
Tue 3 NovObdam 07:29+1 min+1 min
Mon 2 NovObdam 07:29No data—
Sat 31 OctHaarlem 07:08+1 min+1 min
Fri 30 OctObdam 07:290 min—
Thu 29 OctObdam 07:290 min—
Wed 28 OctObdam 07:290 min—
Tue 27 OctObdam 07:290 min—
Mon 26 OctObdam 07:30+1 min—
Sat 24 OctObdam 07:30+1 min—
Fri 23 OctObdam 07:33+4 min+4 min
Thu 22 OctObdam 07:33+4 min+5 min
Wed 21 OctObdam 07:290 min—
Tue 20 OctObdam 07:300 min—
Mon 19 OctObdam 07:300 min—
Sat 17 OctObdam 07:290 min—
Fri 16 OctHeemskerk 06:51+2 min+2 min
Thu 15 OctObdam 07:290 min—
Wed 14 OctObdam 07:290 min—
Tue 13 OctObdam 07:290 min—