Train NS 4175 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 19:18 → Hoofddorp 20:22 Daily 1 h 04 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 19:18 from Hoorn Kersenboogerd · Fri 6 Nov

Next departure 19:18 today · Hoorn Kersenboogerd
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 8 full · 5 partial · 16 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 10 full · 5 partial · 42 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: 0 min

Last 30 days

Arrival delay at Hoofddorp, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 50% W n=2
  • 100% T n=2
  • 100% F n=2
  • 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, 15 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
19:18on time on time
19:22 / 19:23≈ on time ≈ on time
19:35≈ on time ≈ +1 min
19:37≈ on time ≈ +1 min
19:40≈ on time ≈ +1 min
19:47≈ on time ≈ +1 min
19:50≈ on time ≈ +1 min
19:56 / 20:06≈ on time ≈ +2 min
20:10≈ on time ≈ +2 min
20:16 / 20:17≈ on time ≈ +3 min
20:22on time +3 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 5 Nov— 20:24No data—
Wed 4 Nov— 20:28+3 min+3 min
Tue 3 Nov— 20:23No data—
Mon 2 Nov— 20:23No data—
Sun 1 NovSchiphol Airport 20:29Partial coverage0 min—
Sat 31 OctSchiphol Airport 20:31Partial coverage0 min—
Fri 30 Oct— 20:23No data—
Thu 29 Oct— 20:200 min—
Wed 28 Oct— 20:230 min—
Tue 27 Oct— 20:24No data—
Mon 26 OctZaandam Kogerveld 20:38No data—
Sun 25 OctSchiphol Airport 20:31No data—
Sat 24 OctSchiphol Airport 20:32No data—
Fri 23 OctHoorn 20:23Partial coverage0 min+1 min
Thu 22 Oct— 20:24No data—
Wed 21 Oct— 20:24No data—
Tue 20 Oct— 20:23No data—
Mon 19 Oct— 20:240 min—
Sun 18 OctSchiphol Airport 20:310 min—
Sat 17 OctSchiphol Airport 20:31No data—
Fri 16 OctZaandam Kogerveld 20:27No data—
Thu 15 Oct— 20:26No data—
Wed 14 OctZaandam Kogerveld 20:35No data—
Tue 13 Oct— 20:23No data—
Mon 12 Oct— 20:230 min—
Sun 11 OctSchiphol Airport 20:31Partial coverage0 min—
Sat 10 OctSchiphol Airport 20:31Partial coverage0 min—
Fri 9 Oct— 20:230 min—
Thu 8 Oct— 21:240 min—
Tue 6 Oct— 20:230 min—