Train NS 4112 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 06:13 → Hoorn Kersenboogerd 07:12 Mon, Tue, Wed, Thu, Fri, Sat 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 05:58

Position estimated from the timetable

Heading to Hoorn Kersenboogerd 0 min

Estimated arrival at Hoorn Kersenboogerd 07:12

  1. Hoofddorp06:13
  2. Amsterdam Lelylaan06:25
  3. Amsterdam Sloterdijk06:29
  4. Zaandam Kogerveld06:42
  5. Purmerend06:51
  6. Purmerend Overwhere06:54
  7. Hoorn Kersenboogerd07:12

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 21 runs arrived on time.

On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 6 full · 15 partial · 4 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 9 full · 24 partial · 42 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 33
  • 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=7
  • 100% W n=7
  • 100% T n=5
  • 100% F n=5
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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 10Today
06:13on time on time
06:17 / 06:18≈ on time ≈ on time
06:25≈ on time ≈ on time
06:29 / 06:31≈ on time ≈ on time
06:38≈ on time ≈ on time
06:42≈ on time ≈ on time
06:48≈ on time ≈ on time
06:51≈ on time ≈ on time
06:54≈ on time ≈ on time
07:05 / 07:08≈ on time ≈ +1 min
07:12on 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 18 NovHoorn 07:22Partial coverage0 min—
Tue 17 NovHoorn 07:22Partial coverage0 min—
Mon 16 NovHoorn 07:22Partial coverage0 min—
Sat 14 NovHoorn 07:220 min—
Fri 13 NovHoorn 07:220 min—
Thu 12 NovHoorn 07:22Partial coverage0 min—
Wed 11 NovHoorn 07:23Partial coverage0 min—
Tue 10 NovHoorn 07:22Partial coverage0 min—
Mon 9 NovHoorn 07:22Partial coverage0 min—
Sat 7 NovHoorn 07:230 min—
Fri 6 NovHoorn 07:25No data—
Thu 5 NovHoorn 07:23No data—
Wed 4 NovHoorn 07:22Partial coverage0 min—
Tue 3 NovHoorn 07:24Partial coverage+3 min+4 min
Mon 2 NovHoorn 07:22No data—
Sat 31 OctHoorn 07:22No data—
Fri 30 OctHoorn 07:220 min—
Thu 29 OctHoorn 07:22Partial coverage0 min—
Wed 28 OctHoorn 07:24Partial coverage+2 min+2 min
Tue 27 OctHoorn 07:22Partial coverage0 min—
Mon 26 OctHoorn 07:22Partial coverage0 min—
Sat 24 OctHoorn 07:220 min—
Fri 23 OctHoorn 07:24+1 min+2 min
Thu 22 OctHoorn 07:22Partial coverage0 min—
Wed 21 OctHoorn 07:22Partial coverage0 min—
Tue 20 OctHoorn 07:22Partial coverage0 min—
Mon 19 OctHoorn 07:22Partial coverage0 min—
Sat 17 OctHoorn 07:22No data—
Fri 16 OctHoorn 07:220 min—
Thu 15 OctHoorn 07:23Partial coverage+1 min+3 min