Train NS 4142 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 13:38 → Hoorn Kersenboogerd 14: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 13:38 from Hoofddorp · Thu 5 Nov

Next departure 13:38 today · Hoofddorp
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 15 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 10 full · 6 partial · 72 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: +2 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 +8 min · last fix heading to Hoorn +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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