Train NS 4837 Amsterdam Centraal – Hoorn

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 12:25 from Amsterdam Centraal · Tue 17 Nov

Next departure 12:25 today · Amsterdam Centraal
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 16 full · 6 partial · 7 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 27 full · 6 partial · 55 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 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 9 Oct Max en route +7 min · last fix heading to Alkmaar Noord +7 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Heiloo +5 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Santpoort Zuid +3 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 91% · 30
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 100% W n=5
  • 100% T n=6
  • 75% F n=4
  • 80% 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, 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
12:25on time on time
12:31≈ on time ≈ on time
12:36≈ on time ≈ on time
12:40≈ on time ≈ on time
12:44 / 12:45≈ on time ≈ on time
12:49≈ on time ≈ +1 min
12:52≈ on time ≈ +1 min
12:54≈ on time ≈ +1 min
12:57≈ on time ≈ +1 min
13:02≈ on time ≈ +1 min
13:06≈ on time ≈ +1 min
13:10 / 13:11≈ on time ≈ +1 min
13:15≈ on time ≈ +1 min
13:21≈ on time ≈ +1 min
13:26 / 13:31≈ on time ≈ +2 min
13:34≈ on time ≈ +2 min
13:39≈ on time ≈ +2 min
13:44 / 13:45≈ on time ≈ +2 min
13:54on 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 13:59Partial coverage+1 min—
Sun 15 NovObdam 14:000 min—
Sat 14 NovObdam 13:590 min—
Fri 13 NovHeiloo 13:340 min—
Thu 12 NovHeiloo 13:340 min—
Wed 11 NovHeiloo 13:34+1 min—
Tue 10 NovHeiloo 13:39+5 min+6 min
Mon 9 NovHeiloo 13:340 min—
Sun 8 NovObdam 13:59+2 min+2 min
Sat 7 NovObdam 13:590 min—
Fri 6 NovObdam 13:59No data—
Thu 5 NovObdam 13:590 min—
Wed 4 NovObdam 13:59+1 min—
Tue 3 NovObdam 14:09No data—
Mon 2 NovObdam 13:59No data—
Sun 1 NovSantpoort Zuid 13:09+1 min+1 min
Sat 31 OctSantpoort Zuid 13:09+3 min+3 min
Fri 30 OctObdam 14:000 min—
Thu 29 OctObdam 13:59Partial coverage0 min—
Wed 28 OctObdam 14:00Partial coverage0 min—
Tue 27 OctObdam 13:59Partial coverage0 min—
Mon 26 OctObdam 13:59No data—
Sun 25 OctObdam 13:59No data—
Sat 24 OctObdam 13:590 min—
Fri 23 OctObdam 13:590 min—
Thu 22 OctObdam 13:59Partial coverage0 min—
Wed 21 OctObdam 13:59No data—
Tue 20 OctObdam 14:00No data—
Mon 19 OctObdam 13:59Partial coverage0 min—
Sun 18 OctObdam 14:000 min—