Train NS 4146 Hoofddorp – Hoorn Kersenboogerd

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 14:38 from Hoofddorp · Fri 20 Nov

Next departure 14:38 today · Hoofddorp
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 10 full · 13 partial · 6 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 16 full · 18 partial · 54 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: 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

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=3
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

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