Train NS 4130 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 10:38 → Hoorn Kersenboogerd 11:37 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 10:51

Heading to Hoorn Kersenboogerd 0 min

Estimated arrival at Hoorn Kersenboogerd 11:37 · 1 km/h

  1. Hoofddorp10:38
  2. Amsterdam Lelylaan10:50
  3. Amsterdam Sloterdijk10:54
  4. Zaandam Kogerveld11:08
  5. Purmerend11:18
  6. Purmerend Overwhere11:20
  7. Hoorn Kersenboogerd11:37

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 19 runs arrived on time.

On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 8 full · 11 partial · 11 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 12 full · 14 partial · 63 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 Kersenboogerd, in minutes. One bar per run.

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

Worst days

  • Thu 12 Nov Max en route +3 min · last fix heading to Hoorn +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
10:38on time on time
10:42 / 10:43≈ on time ≈ on time
10:50≈ on time ≈ on time
10:54 / 10:58≈ on time ≈ on time
11:04≈ on time ≈ on time
11:08≈ on time ≈ on time
11:15≈ on time ≈ on time
11:18≈ on time ≈ on time
11:20≈ on time ≈ +1 min
11:32 / 11:34≈ on time ≈ +1 min
11:37on 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
Tue 17 NovAmsterdam Lelylaan 10:49Partial coverage0 min—
Mon 16 NovHoorn 11:49Partial coverage0 min—
Sun 15 NovHoorn 11:530 min—
Sat 14 NovHoorn 11:520 min—
Fri 13 NovHoorn 11:52+1 min—
Thu 12 NovHoorn 11:49Partial coverage+3 min+3 min
Wed 11 NovHoorn 11:48Partial coverage0 min—
Tue 10 NovHoorn 11:48Partial coverage0 min+2 min
Mon 9 NovHoorn 11:48Partial coverage0 min—
Sun 8 NovHoorn 11:520 min—
Sat 7 NovHoorn 11:53+1 min—
Fri 6 NovHoorn 11:52No data—
Thu 5 NovHoorn 11:48No data—
Wed 4 NovHoorn 11:48Partial coverage0 min—
Tue 3 NovHoorn 11:48No data—
Mon 2 NovHoorn 11:48No data—
Sun 1 NovHoorn 11:530 min—
Sat 31 OctHoorn 11:520 min—
Fri 30 OctHoorn 11:53No data—
Thu 29 OctHoorn 11:48No data—
Wed 28 OctHoorn 11:48Partial coverage0 min—
Tue 27 OctHoorn 11:48Partial coverage0 min—
Mon 26 OctHoorn 11:48No data—
Sun 25 OctHoorn 11:52No data—
Sat 24 OctHoorn 11:520 min—
Fri 23 OctHoorn 11:55No data—
Thu 22 OctHoorn 11:48No data—
Wed 21 OctHoorn 11:48No data—
Tue 20 OctHoorn 11:49Partial coverage0 min—
Mon 19 OctHoorn 11:50Partial coverage0 min—