Train NS 4150 Hoofddorp – Hoorn Kersenboogerd

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 15:38 from Hoofddorp · Wed 18 Nov

Next departure 15:38 today · Hoofddorp
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 8 full · 8 partial · 13 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 13 full · 13 partial · 62 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 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

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

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

On-time by weekday

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