Train NS 4829 Amsterdam Centraal → Hoorn

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

NS 4829 Amsterdam Centraal–Hoorn: final delay under 3 min on 25 of its 26 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 19:30 (GMT+1).

✓ Today’s run finished

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

  1. Amsterdam Centraal10:25
  2. Haarlem Spaarnwoude10:40
  3. Santpoort Zuid10:52
  4. Beverwijk11:02
  5. Castricum11:15
  6. Obdam11:44
  7. Hoorn11:54

Next service: tomorrow 10:25 from Amsterdam Centraal · Mon 23 Nov

Next departure 10:25 tomorrow · Amsterdam Centraal
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 22 full · 4 partial · 4 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 33 full · 4 partial · 52 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

  • Tue 10 Nov Max en route +3 min · last fix heading to Heiloo +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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