Train NS 4835 Amsterdam Centraal – Hoorn

Amsterdam Centraal 11:55 → Hoorn 13:24 Daily 1 h 29 min · 19 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Obdam at 13:29 0 min

  1. Amsterdam Centraal11:55
  2. Haarlem Spaarnwoude12:10
  3. Santpoort Zuid12:22
  4. Beverwijk12:32
  5. Castricum12:45
  6. Obdam13:14
  7. Hoorn13:24

Next service: tomorrow 11:55 from Amsterdam Centraal · Mon 16 Nov

Next departure 11:55 tomorrow · Amsterdam Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 9 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 27 full · 2 partial · 60 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

  • Sat 10 Oct Max en route +4 min · last fix heading to Alkmaar Noord +4 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Heiloo +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 67% F n=3
  • 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, 29 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
11:55on time on time
12:01≈ on time ≈ on time
12:06≈ on time ≈ on time
12:10≈ on time ≈ on time
12:14 / 12:15≈ on time ≈ on time
12:19≈ on time ≈ on time
12:22≈ on time ≈ on time
12:24≈ on time ≈ on time
12:27≈ on time ≈ on time
12:32≈ on time ≈ on time
12:35≈ on time ≈ on time
12:40 / 12:41≈ on time ≈ +1 min
12:45≈ on time ≈ +1 min
12:50≈ on time ≈ +1 min
12:55 / 13:01≈ on time ≈ +1 min
13:04≈ on time ≈ +1 min
13:09≈ on time ≈ +1 min
13:14 / 13:15≈ on time ≈ +1 min
13:24on 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 13:29Partial coverage0 min—
Sat 14 NovObdam 13:29Partial coverage0 min—
Fri 13 NovHeiloo 13:07+3 min+3 min
Thu 12 NovHeiloo 13:04+1 min—
Wed 11 NovHeiloo 13:04+1 min+1 min
Tue 10 NovHeiloo 13:040 min—
Mon 9 NovHeiloo 13:040 min—
Sun 8 NovObdam 13:290 min+1 min
Sat 7 NovObdam 13:290 min—
Fri 6 NovObdam 13:29No data—
Thu 5 NovObdam 13:29No data—
Wed 4 NovObdam 13:29+1 min—
Tue 3 NovObdam 13:290 min—
Mon 2 NovObdam 13:390 min—
Sun 1 NovSantpoort Zuid 12:380 min—
Sat 31 OctSantpoort Zuid 12:370 min—
Fri 30 OctObdam 13:290 min—
Thu 29 OctObdam 13:29No data—
Wed 28 OctObdam 13:320 min—
Tue 27 OctObdam 13:290 min—
Mon 26 OctObdam 13:290 min—
Sun 25 OctObdam 13:29No data—
Sat 24 OctObdam 13:290 min—
Fri 23 OctObdam 13:31No data—
Thu 22 OctObdam 13:30No data—
Wed 21 OctObdam 13:31No data—
Tue 20 OctObdam 13:29No data—
Mon 19 OctObdam 13:290 min—
Sun 18 OctObdam 13:29+1 min—
Sat 17 OctObdam 13:29No data—