Train NS 4180 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 23:08 → Hoorn Kersenboogerd 00:12 Daily 1 h 04 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 23:08 from Hoofddorp · Sat 7 Nov

Full trip card
Next departure 23:08 today · Hoofddorp
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Worst days

  • Mon 19 Oct Max en route +24 min · last fix heading to — +24 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
Hoofddorp
23:08on time on time
Schiphol Airport
23:12 / 23:13≈ on time ≈ on time
Amsterdam Lelylaan
23:20≈ on time ≈ on time
Amsterdam Sloterdijk
23:24 / 23:33≈ on time ≈ on time
Zaandam
23:39≈ on time ≈ on time
Zaandam Kogerveld
23:44≈ on time ≈ on time
Purmerend Weidevenne
23:50≈ on time ≈ on time
Purmerend
23:53≈ on time ≈ on time
Purmerend Overwhere
23:55≈ on time ≈ on time
Hoorn
00:07 / 00:08≈ on time ≈ on time
Hoorn Kersenboogerd
00:12on time on time

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
Fri 6 Nov— 00:130 min—
Thu 5 Nov— 00:340 min—
Wed 4 Nov— 00:290 min—
Tue 3 Nov— 00:140 min—
Mon 2 Nov— 00:140 min—
Sun 1 NovHoorn 00:220 min—
Sat 31 OctSchiphol Airport 00:13No data—
Fri 30 Oct— 00:14No data—
Thu 29 Oct— 00:30+1 min—
Wed 28 Oct— 00:300 min—
Tue 27 Oct— 00:160 min—
Mon 26 Oct— 00:230 min—
Sun 25 OctHoorn 00:23No data—
Sat 24 Oct— 00:14No data—
Fri 23 Oct— 00:140 min—
Thu 22 Oct— 00:330 min—
Wed 21 Oct— 00:350 min—
Tue 20 Oct— 00:220 min—
Mon 19 Oct— 01:00+24 min+24 min
Sun 18 OctHoorn 00:220 min—
Sat 17 OctHoorn 00:220 min—
Fri 16 Oct— 00:130 min—
Thu 15 Oct— 00:410 min—
Wed 14 Oct— 00:300 min—
Tue 13 Oct— 00:18No data—
Mon 12 Oct— 00:130 min—
Sun 11 OctHoorn 00:23+1 min—
Sat 10 Oct— 06:250 min+2 min
Fri 9 Oct— 00:130 min—
Thu 8 Oct— 00:310 min—