Train NS 4853 Amsterdam Centraal – Hoorn

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 16:25 from Amsterdam Centraal · Mon 16 Nov

Next departure 16:25 today · Amsterdam Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 16 full · 5 partial · 8 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 25 full · 5 partial · 58 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: +1 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

  • Wed 11 Nov Max en route +8 min · last fix heading to Heiloo +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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