Train NS 4110 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 05:43 → Hoorn Kersenboogerd 06:42 Mon, Tue, Wed, Thu, Fri 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Hoorn at 06:52 0 min

  1. Hoofddorp05:43
  2. Amsterdam Lelylaan05:55
  3. Amsterdam Sloterdijk05:59
  4. Zaandam Kogerveld06:14
  5. Purmerend06:23
  6. Hoorn06:37
  7. Hoorn Kersenboogerd06:42

Next service: tomorrow 05:43 from Hoofddorp · Thu 19 Nov

Next departure 05:43 tomorrow · Hoofddorp
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 1 full · 20 partial · 1 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 2 full · 29 partial · 32 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=6
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 31 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
05:43on time on time
05:47 / 05:48— —
05:55— —
05:59 / 06:03— —
06:09— —
06:14— —
06:20— —
06:23— —
06:25— —
06:37 / 06:38— —
06:42— —

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 06:52Partial coverage0 min—
Tue 17 NovHoorn 06:54Partial coverage+2 min+2 min
Mon 16 NovHoorn 06:52Partial coverage0 min—
Fri 13 NovHoorn 06:52Partial coverage0 min—
Thu 12 NovHoorn 06:53Partial coverage0 min—
Wed 11 NovHoorn 06:52Partial coverage0 min—
Tue 10 NovHoorn 06:52Partial coverage0 min—
Mon 9 NovHoorn 06:52Partial coverage0 min—
Fri 6 NovHoorn 06:54No data—
Thu 5 NovHoorn 06:53Partial coverage0 min—
Wed 4 NovHoorn 06:52Partial coverage0 min—
Tue 3 NovHoorn 06:52Partial coverage0 min—
Mon 2 NovHoorn 06:530 min—
Fri 30 OctHoorn 06:55Partial coverage+2 min+3 min
Thu 29 OctHoorn 06:52Partial coverage0 min—
Wed 28 OctHoorn 06:52Partial coverage0 min—
Tue 27 OctHoorn 06:52Partial coverage0 min—
Mon 26 OctHoorn 06:53Partial coverage+1 min—
Fri 23 OctHoorn 06:53Partial coverage+1 min—
Thu 22 OctHoorn 06:52Partial coverage0 min—
Wed 21 OctHoorn 06:52Partial coverage0 min—
Tue 20 OctHoorn 06:55Partial coverage+3 min+3 min
Mon 19 OctHoorn 06:52Partial coverage0 min—
Fri 16 OctHoorn 06:520 min—
Thu 15 OctHoorn 06:54Partial coverage+1 min+2 min
Wed 14 OctHoorn 06:52Partial coverage0 min—
Tue 13 OctHoorn 06:52Partial coverage0 min—
Mon 12 OctHoorn 06:53Partial coverage0 min—
Fri 9 OctHoorn 06:52Partial coverage0 min—
Thu 8 OctHoorn 06:52Partial coverage0 min—