Train NS 4813 Amsterdam Centraal – Hoorn

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

✓ Today’s run finished

Today, last fix heading to Obdam at 07:59 +1 min

  1. Amsterdam Centraal06:25
  2. Haarlem Spaarnwoude06:40
  3. Santpoort Zuid06:52
  4. Beverwijk07:02
  5. Castricum07:15
  6. Obdam07:44
  7. Hoorn07:54

Next service: tomorrow 06:25 from Amsterdam Centraal · Tue 17 Nov

Next departure 06:25 tomorrow · Amsterdam Centraal
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 3 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 38 full · 1 partial · 50 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: +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 13 Nov Max en route +4 min · last fix heading to Heiloo +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Heiloo +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 37
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
06:25on time on time
06:30≈ on time ≈ on time
06:35≈ on time ≈ on time
06:40≈ on time ≈ on time
06:43 / 06:45≈ on time ≈ on time
06:49≈ on time ≈ +1 min
06:52≈ on time ≈ +1 min
06:54≈ on time ≈ +1 min
06:57≈ on time ≈ +1 min
07:02≈ on time ≈ +1 min
07:06≈ on time ≈ +1 min
07:10 / 07:11≈ on time ≈ +1 min
07:15≈ on time ≈ +1 min
07:21≈ on time ≈ +1 min
07:26 / 07:31≈ on time ≈ +1 min
07:34≈ on time ≈ +2 min
07:39≈ on time ≈ +2 min
07:44 / 07:45≈ on time ≈ +2 min
07: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 07:59Partial coverage+1 min+1 min
Sun 15 NovObdam 07:59+1 min+2 min
Sat 14 NovObdam 07:59+1 min+2 min
Fri 13 NovHeiloo 07:42+4 min+4 min
Thu 12 NovHeiloo 07:34+2 min+2 min
Wed 11 NovHeiloo 07:37+2 min+2 min
Tue 10 NovHeiloo 07:38+3 min+3 min
Mon 9 NovHeiloo 07:37+2 min+2 min
Sun 8 NovObdam 07:590 min—
Sat 7 NovObdam 08:000 min—
Fri 6 NovObdam 07:59No data—
Thu 5 NovObdam 07:590 min—
Wed 4 NovObdam 07:59+1 min+1 min
Tue 3 NovObdam 07:590 min—
Mon 2 NovObdam 07:59No data—
Sun 1 NovSantpoort Zuid 07:07+2 min+2 min
Sat 31 OctSantpoort Zuid 07:07+2 min+2 min
Fri 30 OctObdam 08:02+2 min+2 min
Thu 29 OctObdam 08:000 min—
Wed 28 OctObdam 08:000 min—
Tue 27 OctObdam 07:590 min—
Mon 26 OctObdam 07:590 min—
Sun 25 OctObdam 07:59No data—
Sat 24 OctObdam 07:59+1 min—
Fri 23 OctObdam 08:00+1 min—
Thu 22 OctObdam 08:040 min—
Wed 21 OctObdam 07:590 min—
Tue 20 OctObdam 08:000 min—
Mon 19 OctObdam 08:000 min—
Sun 18 OctObdam 07:590 min—