Train NS 4123 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 06:18 → Hoofddorp 07:22 Mon, Tue, Wed, Thu, Fri 1 h 04 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 07:29 0 min

  1. Hoorn Kersenboogerd06:18
  2. Purmerend Overwhere06:35
  3. Purmerend06:37
  4. Zaandam Kogerveld06:47
  5. Amsterdam Sloterdijk06:56
  6. Schiphol Airport07:16
  7. Hoofddorp07:22

Next service: Monday 06:18 from Hoorn Kersenboogerd · Mon 23 Nov

Next departure 06:18 Monday · Hoorn Kersenboogerd
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 2 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 30 full · 2 partial · 32 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: +1 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 9 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 31
  • 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=7
  • 100% W n=7
  • 100% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
06:18on time on time
06:22 / 06:23≈ on time ≈ on time
06:35≈ on time ≈ on time
06:37≈ on time ≈ +1 min
06:40≈ on time ≈ +1 min
06:47≈ on time ≈ +1 min
06:50≈ on time ≈ +1 min
06:56 / 07:06≈ on time ≈ +1 min
07:10≈ on time ≈ +1 min
07:16 / 07:17≈ on time ≈ +2 min
07:22on 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 NovSchiphol Airport 07:29Partial coverage0 min—
Thu 19 NovSchiphol Airport 07:300 min—
Wed 18 NovSchiphol Airport 07:290 min—
Tue 17 NovSchiphol Airport 07:320 min—
Mon 16 NovSchiphol Airport 07:290 min—
Fri 13 NovSchiphol Airport 07:29Partial coverage0 min—
Thu 12 NovSchiphol Airport 07:320 min—
Wed 11 NovSchiphol Airport 07:32+1 min+2 min
Tue 10 NovSchiphol Airport 07:290 min—
Mon 9 NovSchiphol Airport 07:320 min—
Fri 6 NovSchiphol Airport 07:30No data—
Thu 5 NovSchiphol Airport 07:32No data—
Wed 4 NovSchiphol Airport 07:320 min—
Tue 3 NovSchiphol Airport 07:290 min+1 min
Mon 2 NovSchiphol Airport 07:290 min—
Fri 30 OctSchiphol Airport 07:320 min—
Thu 29 OctSchiphol Airport 07:32+1 min—
Wed 28 OctSchiphol Airport 07:330 min—
Tue 27 OctSchiphol Airport 07:33+1 min+1 min
Mon 26 OctSchiphol Airport 07:320 min—
Fri 23 OctSchiphol Airport 07:310 min—
Thu 22 OctSchiphol Airport 07:320 min—
Wed 21 OctSchiphol Airport 07:310 min—
Tue 20 OctSchiphol Airport 07:38+2 min+3 min
Mon 19 OctSchiphol Airport 07:320 min—
Fri 16 OctSchiphol Airport 07:32+1 min—
Thu 15 OctSchiphol Airport 07:310 min—
Wed 14 OctSchiphol Airport 07:310 min—
Tue 13 OctSchiphol Airport 07:310 min—
Mon 12 OctSchiphol Airport 07:320 min—