Train NS 4849 Beverwijk – Hoorn

Beverwijk 16:02 → Hoorn 16:54 Daily 0 h 52 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Obdam at 16:59 No data

  1. Beverwijk16:02
  2. Uitgeest16:10
  3. Castricum16:16
  4. Alkmaar16:26
  5. Alkmaar Noord16:34
  6. Obdam16:44
  7. Hoorn16:54

Next service: tomorrow 16:02 from Beverwijk · Sat 7 Nov

Next departure 16:02 tomorrow · Beverwijk
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 9 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 22 full · 2 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 9 Oct Max en route +5 min · last fix heading to Alkmaar Noord +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=3
  • 100% T n=4
  • 67% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 24 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:02on time on time
16:06≈ on time ≈ on time
16:10 / 16:11≈ on time ≈ on time
16:16≈ on time ≈ on time
16:21≈ on time ≈ on time
16:26 / 16:31≈ on time ≈ on time
16:34≈ on time ≈ on time
16:39≈ on time ≈ on time
16:44 / 16:45≈ on time ≈ on time
16:54on time on time

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
Fri 6 NovObdam 16:59No data—
Thu 5 NovObdam 16:59No data—
Wed 4 NovObdam 16:59Partial coverage0 min—
Tue 3 NovObdam 16:59No data—
Mon 2 NovObdam 16:59Partial coverage0 min—
Sun 1 NovSantpoort Zuid 16:070 min—
Sat 31 OctSantpoort Zuid 16:060 min—
Fri 30 OctObdam 16:590 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:00+1 min+1 min
Fri 23 OctObdam 16:590 min—
Thu 22 OctObdam 16:590 min—
Wed 21 OctObdam 16:59No data—
Tue 20 OctObdam 16:590 min—
Mon 19 OctObdam 17:140 min—
Sun 18 OctObdam 16:590 min—
Sat 17 OctObdam 17:00No data—
Fri 16 OctHeemskerk 16:20No data—
Thu 15 OctObdam 16:590 min—
Wed 14 OctObdam 16:59No data—
Tue 13 OctObdam 16:59No data—
Mon 12 OctAlkmaar Noord 16:490 min—
Sun 11 OctAlkmaar Noord 16:480 min—
Sat 10 OctAlkmaar Noord 16:490 min—
Fri 9 OctAlkmaar Noord 16:53+4 min+5 min
Thu 8 OctAlkmaar Noord 16:480 min—