Train NS 4126 Hoofddorp – Hoorn Kersenboogerd

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 09:38 from Hoofddorp · Thu 5 Nov

Next departure 09:38 today · Hoofddorp
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 12 full · 8 partial · 9 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 12 full · 9 partial · 67 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

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

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

On-time by weekday

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