Train NS 4152 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 16:08 → Hoorn Kersenboogerd 17:07 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 16:08 from Hoofddorp · Fri 6 Nov

Next departure 16:08 today · Hoofddorp
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 10 full · 5 partial · 14 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 11 full · 7 partial · 70 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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:08on time on time
16:12 / 16:13≈ on time ≈ on time
16:20≈ on time ≈ on time
16:24 / 16:28≈ on time ≈ on time
16:34≈ on time ≈ on time
16:38≈ on time ≈ on time
16:45≈ on time ≈ on time
16:48≈ on time ≈ on time
16:50≈ on time ≈ on time
17:02 / 17:04≈ on time ≈ +1 min
17:07on 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
Thu 5 NovHoorn 17:19No data—
Wed 4 NovHoorn 17:18Partial coverage0 min—
Tue 3 NovHoorn 17:18No data—
Mon 2 NovHoorn 17:18No data—
Sun 1 NovHoorn 17:220 min—
Sat 31 OctHoorn 17:220 min—
Fri 30 OctHoorn 17:22No data—
Thu 29 OctHoorn 17:18Partial coverage0 min—
Wed 28 OctHoorn 17:180 min—
Tue 27 OctHoorn 17:18Partial coverage0 min—
Mon 26 OctHoorn 17:22No data—
Sun 25 OctHoorn 17:23No data—
Sat 24 OctHoorn 17:220 min—
Fri 23 OctHoorn 17:240 min—
Thu 22 OctHoorn 17:18No data—
Wed 21 OctHoorn 17:24No data—
Tue 20 OctHoorn 17:21No data—
Mon 19 OctHoorn 17:22No data—
Sun 18 OctHoorn 17:230 min+2 min
Sat 17 OctHoorn 17:240 min—
Fri 16 OctHoorn 17:22No data—
Thu 15 OctHoorn 17:17No data—
Wed 14 OctHoorn 17:20No data—
Tue 13 OctHoorn 17:18No data—
Mon 12 OctHoorn 17:19Partial coverage0 min—
Sun 11 OctHoorn 17:23+1 min—
Sat 10 OctHoorn 17:220 min—
Fri 9 OctHoorn 17:24+2 min+2 min
Thu 8 OctHoorn 17:18Partial coverage0 min—
Wed 7 OctHoorn 17:21Partial coverage+1 min+3 min