Train NS 4849 Amsterdam Centraal → Hoorn

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

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

It has not run yet today

Last recorded run: Saturday 21 November +5 min

Next service: today 15:25 from Amsterdam Centraal · Sun 22 Nov

Next departure 15:25 today · Amsterdam Centraal
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 20 full · 5 partial · 4 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 33 full · 6 partial · 49 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: +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

  • Sat 21 Nov Max en route +6 min · last fix heading to Obdam +5 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Alkmaar Noord +4 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=7
  • 100% T n=5
  • 100% W n=5
  • 100% T n=6
  • 80% F n=5
  • 83% 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
15:25on time on time
15:31≈ on time ≈ on time
15:36≈ on time ≈ on time
15:40≈ on time ≈ on time
15:44 / 15:45≈ on time ≈ on time
15:49≈ on time ≈ on time
15:52≈ on time ≈ on time
15:54≈ on time ≈ on time
15:57≈ on time ≈ on time
16:02≈ on time ≈ +1 min
16:05≈ on time ≈ +1 min
16:10 / 16:11≈ on time ≈ +1 min
16:15≈ on time ≈ +1 min
16:20≈ on time ≈ +1 min
16:25 / 16:31≈ on time ≈ +1 min
16:34≈ on time ≈ +1 min
16:39≈ on time ≈ +1 min
16:44 / 16:45≈ on time ≈ +1 min
16: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
Sat 21 NovObdam 17:04Partial coverage+5 min+6 min
Fri 20 NovObdam 16:590 min—
Thu 19 NovObdam 16:590 min—
Wed 18 NovObdam 16:59+1 min—
Tue 17 NovObdam 16:590 min—
Mon 16 NovObdam 17:00+2 min+2 min
Sun 15 NovObdam 16:59Partial coverage0 min—
Sat 14 NovObdam 16:59Partial coverage0 min—
Fri 13 NovHeiloo 16:34+1 min+1 min
Thu 12 NovHeiloo 16:37+2 min+2 min
Wed 11 NovHeiloo 16:340 min—
Tue 10 NovHeiloo 16:340 min—
Mon 9 NovHeiloo 16:380 min+2 min
Sun 8 NovObdam 17:000 min—
Sat 7 NovObdam 16:590 min—
Fri 6 NovObdam 16:59No data—
Thu 5 NovObdam 16:59No data—
Wed 4 NovObdam 16:590 min—
Tue 3 NovObdam 16:59No data—
Mon 2 NovObdam 16:590 min—
Sun 1 NovSantpoort Zuid 16:070 min—
Sat 31 OctSantpoort Zuid 16:060 min—
Fri 30 OctObdam 16:59Partial coverage0 min—
Thu 29 OctObdam 16:590 min—
Wed 28 OctObdam 17:000 min—
Tue 27 OctObdam 17:040 min—
Mon 26 OctObdam 16:590 min—
Sun 25 OctObdam 16:59No data—
Sat 24 OctObdam 17:00Partial coverage+1 min+1 min
Fri 23 OctObdam 16:590 min—