Train NS 4177 Hoorn Kersenboogerd → Hoofddorp

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

It has not run yet today

Last recorded run: Friday 20 November +2 min

Next service: today 19:48 from Hoorn Kersenboogerd · Sat 21 Nov

Next departure 19:48 today · Hoorn Kersenboogerd
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 16 full · 5 partial · 7 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 25 full · 9 partial · 24 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 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

  • Fri 23 Oct Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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:48on time on time
19:52 / 19:53≈ on time ≈ on time
20:05≈ on time ≈ +1 min
20:07≈ on time ≈ +1 min
20:10≈ on time ≈ +1 min
20:17≈ on time ≈ +1 min
20:20≈ on time ≈ +1 min
20:26 / 20:36≈ on time ≈ +1 min
20:40≈ on time ≈ +2 min
20:46 / 20:47≈ on time ≈ +2 min
20:52on time +2 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
Fri 20 Nov— 20:58+2 min+2 min
Thu 19 Nov— 20:540 min—
Wed 18 Nov— 20:530 min—
Tue 17 Nov— 20:54+2 min+2 min
Mon 16 Nov— 20:540 min—
Sun 15 NovSchiphol Airport 21:02Partial coverage+2 min+2 min
Sat 14 NovSchiphol Airport 20:59Partial coverage0 min—
Fri 13 Nov— 20:53+2 min+2 min
Thu 12 Nov— 20:490 min—
Wed 11 Nov— 20:530 min—
Tue 10 Nov— 20:530 min—
Mon 9 Nov— 20:530 min—
Sun 8 NovAmsterdam Lelylaan 20:480 min—
Sat 7 NovZaandam 20:34Partial coverage0 min—
Fri 6 Nov— 20:58+2 min+3 min
Thu 5 Nov— 20:54No data—
Wed 4 Nov— 20:59+3 min+4 min
Tue 3 Nov— 20:53No data—
Mon 2 Nov— 20:530 min—
Sun 1 NovSchiphol Airport 20:59Partial coverage0 min—
Sat 31 OctSchiphol Airport 21:01Partial coverage0 min—
Fri 30 Oct— 20:57No data—
Wed 28 Oct— 20:53No data—
Tue 27 Oct— 20:540 min—
Mon 26 OctHoorn Kersenboogerd 20:53No data—
Sun 25 OctSchiphol Airport 21:01No data—
Sat 24 OctSchiphol Airport 21:04No data—
Fri 23 Oct— 21:02+3 min+5 min
Thu 22 Oct— 20:54No data—
Wed 21 Oct— 20:53No data—