Train NS 4858 Hoorn – Amsterdam Centraal

Hoorn 17:36 → Amsterdam Centraal 19:05 Daily 1 h 29 min · 19 stops NS (Nederlandse Spoorwegen)

Running now · updated 17:56

Heading to Amsterdam Centraal No data

Estimated arrival at Amsterdam Centraal 19:05

  1. Hoorn17:36
  2. Alkmaar Noord17:56
  3. Castricum18:14
  4. Beverwijk18:27
  5. Santpoort Zuid18:38
  6. Haarlem Spaarnwoude18:50
  7. Amsterdam Centraal19:05
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 8 full · 10 partial · 12 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 14 full · 10 partial · 65 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 Amsterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

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 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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 10Today
17:36on time on time
17:44 / 17:45≈ on time ≈ on time
17:51≈ on time ≈ on time
17:56≈ on time ≈ on time
17:59 / 18:04≈ on time ≈ on time
18:09≈ on time ≈ on time
18:14≈ on time ≈ on time
18:19≈ on time ≈ on time
18:24≈ on time ≈ on time
18:27 / 18:28≈ on time ≈ on time
18:33≈ on time ≈ on time
18:35≈ on time ≈ on time
18:38≈ on time ≈ on time
18:41≈ on time ≈ on time
18:45 / 18:47≈ on time ≈ on time
18:50≈ on time ≈ +1 min
18:55≈ on time ≈ +1 min
19:00≈ on time ≈ +1 min
19:05on 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
Mon 9 NovAlkmaar 17:54No data—
Sun 8 NovAmsterdam Sloterdijk 19:14Partial coverage+1 min—
Sat 7 NovAmsterdam Sloterdijk 19:14Partial coverage0 min—
Fri 6 NovHeemskerk 18:370 min+1 min
Thu 5 NovCastricum 18:27No data—
Wed 4 NovCastricum 18:29No data—
Tue 3 NovHeiloo 18:28No data—
Mon 2 NovHeiloo 18:27No data—
Sun 1 NovAmsterdam Sloterdijk 19:14+1 min—
Sat 31 OctAmsterdam Sloterdijk 19:140 min—
Fri 30 OctHaarlem Spaarnwoude 19:07No data—
Thu 29 OctAlkmaar Noord 19:06Partial coverage+1 min—
Wed 28 OctHeiloo 19:06Partial coverage0 min—
Tue 27 OctAlkmaar 19:07Partial coverage0 min—
Mon 26 OctHeiloo 19:06Partial coverage0 min—
Sun 25 OctAmsterdam Sloterdijk 19:17No data—
Sat 24 OctAmsterdam Sloterdijk 19:14Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 19:140 min—
Thu 22 OctBloemendaal 19:07Partial coverage0 min—
Wed 21 OctSantpoort Zuid 19:07No data—
Tue 20 OctBloemendaal 19:06Partial coverage0 min—
Mon 19 OctBloemendaal 18:55No data—
Sun 18 OctAmsterdam Sloterdijk 19:14Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 19:14No data—
Fri 16 OctAmsterdam Sloterdijk 19:14No data—
Thu 15 OctHeemskerk 19:060 min—
Wed 14 OctHoorn 19:130 min—
Tue 13 OctSantpoort Zuid 19:09No data—
Mon 12 OctBloemendaal 19:080 min—
Sun 11 OctHaarlem 19:280 min+8 min