Train NS 4160 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 18:08 → Hoorn Kersenboogerd 19:07 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 18:08 from Hoofddorp · Wed 18 Nov

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

  • Mon 16 Nov Max en route +17 min · last fix heading to Amsterdam Lelylaan +13 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Schiphol Airport +6 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Hoorn +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
18:08on time on time
18:12 / 18:13≈ on time ≈ on time
18:20≈ on time ≈ on time
18:24 / 18:28≈ on time ≈ +1 min
18:34≈ on time ≈ +1 min
18:38≈ on time ≈ +1 min
18:45≈ on time ≈ +1 min
18:48≈ on time ≈ +1 min
18:50≈ on time ≈ +1 min
19:02 / 19:04≈ on time ≈ +1 min
19:07on 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
Tue 17 NovAmsterdam Lelylaan 19:08Partial coverage+1 min—
Mon 16 NovAmsterdam Lelylaan 19:24Partial coverage+13 min+17 min
Sun 15 NovHoorn 19:220 min—
Sat 14 NovHoorn 19:220 min—
Fri 13 NovPurmerend Overwhere 19:140 min—
Thu 12 NovAmsterdam Lelylaan 19:09Partial coverage0 min—
Wed 11 NovSchiphol Airport 19:09Partial coverage0 min—
Tue 10 NovAmsterdam Lelylaan 19:09Partial coverage0 min—
Mon 9 NovSchiphol Airport 19:14Partial coverage+6 min+6 min
Sun 8 NovHoorn 19:230 min—
Sat 7 NovHoorn 19:220 min—
Fri 6 NovZaandam Kogerveld 19:14+1 min—
Thu 5 NovSchiphol Airport 19:08No data—
Wed 4 NovSchiphol Airport 19:09No data—
Tue 3 NovHoofddorp 19:09No data—
Mon 2 NovHoofddorp 19:08Partial coverage0 min—
Sun 1 NovHoorn 19:23+1 min—
Sat 31 OctHoorn 19:220 min—
Fri 30 OctPurmerend 19:20No data—
Thu 29 Oct— 19:080 min—
Wed 28 OctSchiphol Airport 19:08Partial coverage0 min—
Tue 27 Oct— 19:10No data—
Mon 26 OctHoofddorp 19:08No data—
Sun 25 OctHoorn 19:22No data—
Sat 24 OctHoorn 19:220 min—
Fri 23 OctPurmerend Overwhere 19:370 min+17 min
Thu 22 OctPurmerend Weidevenne 19:09No data—
Wed 21 OctZaandam Kogerveld 19:09No data—
Tue 20 OctPurmerend Weidevenne 19:09No data—
Mon 19 OctZaandam Kogerveld 19:06Partial coverage0 min—