Train NS 4842 Hoorn – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 13:36 from Hoorn · Wed 18 Nov

Next departure 13:36 today · Hoorn
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 19 full · 2 partial · 8 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 29 full · 2 partial · 57 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 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

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

  • Early 0% · 0
  • On time 100% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 100% 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, 31 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
13:36on time on time
13:44 / 13:45≈ on time ≈ on time
13:51≈ on time ≈ on time
13:56≈ on time ≈ on time
13:59 / 14:04≈ on time ≈ on time
14:09≈ on time ≈ +1 min
14:14≈ on time ≈ +1 min
14:19≈ on time ≈ +1 min
14:24≈ on time ≈ +1 min
14:27 / 14:28≈ on time ≈ +1 min
14:33≈ on time ≈ +1 min
14:35≈ on time ≈ +1 min
14:38≈ on time ≈ +1 min
14:41≈ on time ≈ +1 min
14:45 / 14:47≈ on time ≈ +1 min
14:50≈ on time ≈ +1 min
14:55≈ on time ≈ +1 min
15:00≈ on time ≈ +2 min
15:05on time +2 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
Tue 17 NovAmsterdam Sloterdijk 15:14Partial coverage0 min—
Mon 16 NovAmsterdam Sloterdijk 15:19+3 min+4 min
Sun 15 NovAmsterdam Sloterdijk 15:140 min—
Sat 14 NovAmsterdam Sloterdijk 15:29Partial coverage0 min—
Fri 13 NovAmsterdam Sloterdijk 15:14+2 min+2 min
Thu 12 NovAmsterdam Sloterdijk 15:15+1 min+4 min
Wed 11 NovAmsterdam Sloterdijk 15:140 min—
Tue 10 NovAmsterdam Sloterdijk 15:140 min—
Mon 9 NovAmsterdam Sloterdijk 15:17+3 min+3 min
Sun 8 NovAmsterdam Sloterdijk 15:140 min—
Sat 7 NovAmsterdam Sloterdijk 15:140 min—
Fri 6 NovHeemskerk 14:38No data—
Thu 5 NovHeemskerk 14:37No data—
Wed 4 NovHeemskerk 14:370 min—
Tue 3 NovAlkmaar 15:04No data—
Mon 2 NovHeemskerk 14:370 min—
Sun 1 NovAmsterdam Sloterdijk 15:160 min—
Sat 31 OctAmsterdam Sloterdijk 15:150 min—
Fri 30 OctAmsterdam Sloterdijk 15:180 min—
Thu 29 OctAmsterdam Sloterdijk 15:150 min—
Wed 28 OctAmsterdam Sloterdijk 15:160 min—
Tue 27 OctAmsterdam Sloterdijk 15:160 min—
Mon 26 OctAmsterdam Sloterdijk 15:150 min—
Sun 25 OctAmsterdam Sloterdijk 15:14No data—
Sat 24 OctAmsterdam Sloterdijk 15:140 min—
Fri 23 OctAmsterdam Sloterdijk 15:15No data—
Thu 22 OctAmsterdam Sloterdijk 15:19No data—
Wed 21 OctAmsterdam Sloterdijk 15:18No data—
Tue 20 OctAmsterdam Sloterdijk 15:16No data—
Mon 19 OctAmsterdam Sloterdijk 15:150 min—