Train NS 4128 Hoofddorp – Hoorn Kersenboogerd

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

✓ Today’s run finished

Today, last fix heading to Hoorn at 11:18 +1 min

  1. Hoofddorp10:08
  2. Amsterdam Lelylaan10:20
  3. Amsterdam Sloterdijk10:24
  4. Zaandam Kogerveld10:38
  5. Purmerend10:48
  6. Hoorn11:02
  7. Hoorn Kersenboogerd11:07

Next service: tomorrow 10:08 from Hoofddorp · Wed 18 Nov

Next departure 10:08 tomorrow · Hoofddorp
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 12 full · 9 partial · 9 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 18 full · 13 partial · 58 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: +1 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=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=2
  • 100% F n=5
  • 100% S n=6
  • 100% S n=5

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
10:08on time on time
10:12 / 10:13≈ on time ≈ on time
10:20≈ on time ≈ on time
10:24 / 10:28≈ on time ≈ on time
10:34≈ on time ≈ +1 min
10:38≈ on time ≈ +1 min
10:45≈ on time ≈ +1 min
10:48≈ on time ≈ +1 min
10:50≈ on time ≈ +1 min
11:02 / 11:04≈ on time ≈ +1 min
11: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 NovHoorn 11:18Partial coverage+1 min—
Mon 16 NovHoorn 11:18Partial coverage+1 min+2 min
Sun 15 NovHoorn 11:230 min—
Sat 14 NovHoorn 11:220 min—
Fri 13 NovHoorn 11:220 min—
Thu 12 NovHoorn 11:18Partial coverage0 min—
Wed 11 NovHoorn 11:19Partial coverage+1 min+1 min
Tue 10 NovHoorn 11:18Partial coverage+1 min—
Mon 9 NovHoorn 11:18Partial coverage0 min—
Sun 8 NovHoorn 11:220 min—
Sat 7 NovHoorn 11:220 min—
Fri 6 NovHoorn 11:22No data—
Thu 5 NovHoorn 11:18No data—
Wed 4 NovHoorn 11:180 min—
Tue 3 NovHoorn 11:19No data—
Mon 2 NovHoorn 11:18Partial coverage0 min—
Sun 1 NovHoorn 11:24+1 min—
Sat 31 OctHoorn 11:220 min—
Fri 30 OctHoorn 11:230 min—
Thu 29 OctHoorn 11:18No data—
Wed 28 OctHoorn 11:18Partial coverage0 min—
Tue 27 OctHoorn 11:180 min—
Mon 26 OctHoorn 11:18No data—
Sun 25 OctHoorn 11:22No data—
Sat 24 OctHoorn 11:230 min—
Fri 23 OctHoorn 11:240 min—
Thu 22 OctHoorn 11:18No data—
Wed 21 OctHoorn 11:18No data—
Tue 20 OctHoorn 11:19Partial coverage0 min—
Mon 19 OctHoorn 11:18No data—