Train NS 4131 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 08:24 → Hoofddorp 09:22 Mon, Tue, Wed, Thu, Fri, Sat 0 h 58 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 09:29 No data

  1. Hoorn Kersenboogerd08:24
  2. Purmerend Overwhere08:39
  3. Purmerend08:42
  4. Zaandam Kogerveld08:51
  5. Amsterdam Sloterdijk09:01
  6. Schiphol Airport09:16
  7. Hoofddorp09:22

Next service: tomorrow 08:24 from Hoorn Kersenboogerd · Sat 7 Nov

Next departure 08:24 tomorrow · Hoorn Kersenboogerd
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 7 full · 9 partial · 10 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 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 Hoofddorp, 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 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=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=3
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 18 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
08:24on time on time
08:27 / 08:28≈ on time ≈ on time
08:39≈ on time ≈ on time
08:42≈ on time ≈ +1 min
08:45≈ on time ≈ +1 min
08:51≈ on time ≈ +1 min
08:55≈ on time ≈ +1 min
09:01 / 09:06≈ on time ≈ +1 min
09:10≈ on time ≈ +1 min
09:16 / 09:17≈ on time ≈ +1 min
09: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 6 NovSchiphol Airport 09:29No data—
Thu 5 NovSchiphol Airport 09:32No data—
Wed 4 NovSchiphol Airport 09:29Partial coverage0 min—
Tue 3 NovSchiphol Airport 09:29No data—
Mon 2 NovSchiphol Airport 09:29Partial coverage0 min—
Sat 31 OctSchiphol Airport 09:270 min—
Fri 30 OctSchiphol Airport 09:310 min—
Thu 29 OctSchiphol Airport 09:31No data—
Wed 28 OctSchiphol Airport 09:31Partial coverage0 min—
Tue 27 OctSchiphol Airport 09:32Partial coverage0 min—
Mon 26 OctSchiphol Airport 09:32Partial coverage0 min—
Sat 24 OctSchiphol Airport 09:28+1 min+1 min
Fri 23 OctSchiphol Airport 09:320 min—
Thu 22 OctSchiphol Airport 09:31No data—
Wed 21 OctSchiphol Airport 09:32No data—
Tue 20 OctSchiphol Airport 09:31Partial coverage0 min—
Mon 19 OctSchiphol Airport 09:31Partial coverage0 min—
Sat 17 OctSchiphol Airport 09:270 min—
Fri 16 OctSchiphol Airport 09:31No data—
Thu 15 OctSchiphol Airport 09:31No data—
Wed 14 OctSchiphol Airport 09:32No data—
Tue 13 OctSchiphol Airport 09:31No data—
Mon 12 OctSchiphol Airport 09:34Partial coverage0 min—
Sat 10 OctSchiphol Airport 09:28+2 min+2 min
Fri 9 OctSchiphol Airport 09:320 min—
Thu 8 OctSchiphol Airport 09:32Partial coverage+1 min+1 min
Wed 7 OctSchiphol Airport 09:31Partial coverage0 min—
Tue 6 OctSchiphol Airport 09:32Partial coverage+1 min+1 min
Mon 5 OctZaandam 09:07No data—
Sat 3 OctSchiphol Airport 09:23No data—