Train NS 4122 Hoofddorp – Hoorn Kersenboogerd

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 08:38 today · Hoofddorp
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 11 full · 7 partial · 11 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 11 full · 8 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Sat 24 Oct Max en route +7 min · last fix heading to Hoorn +7 min
  • Tue 6 Oct Max en route +7 min · last fix heading to Hoorn +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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