Train NS 4135 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 09:24 → Hoofddorp 10:22 Daily 0 h 58 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 10:35 No data

  1. Hoorn Kersenboogerd09:24
  2. Purmerend Overwhere09:39
  3. Purmerend09:42
  4. Zaandam Kogerveld09:51
  5. Amsterdam Sloterdijk10:01
  6. Schiphol Airport10:16
  7. Hoofddorp10:22

Next service: tomorrow 09:24 from Hoorn Kersenboogerd · Fri 23 Oct

Full trip card
Next departure 09:24 tomorrow · Hoorn Kersenboogerd
On-time · 30 days
75%
9/12 runs under 3 min
RT coverage: 7 full · 5 partial · 18 no data
On-time · 90 days
75%
9/12 runs under 3 min
RT coverage: 7 full · 5 partial · 77 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 18 Oct Max en route +9 min · last fix heading to Schiphol Airport +9 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Schiphol Airport +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 9
  • 3–10 min 25% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 67% T n=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 50% S n=2
  • 50% S n=2

Stops and timetable

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

StopSched.
Hoorn Kersenboogerd
09:24
Hoorn
09:27 / 09:28
Purmerend Overwhere
09:39
Purmerend
09:42
Purmerend Weidevenne
09:45
Zaandam Kogerveld
09:51
Zaandam
09:55
Amsterdam Sloterdijk
10:01 / 10:06
Amsterdam Lelylaan
10:10
Schiphol Airport
10:16 / 10:17
Hoofddorp
10:22

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.

Recent runs

DateLast stopFinalMax
Thu 22 OctSchiphol Airport 10:35No data—
Wed 21 OctSchiphol Airport 10:310 min—
Tue 20 OctSchiphol Airport 10:31Partial coverage0 min—
Mon 19 OctSchiphol Airport 10:31Partial coverage0 min—
Sun 18 OctSchiphol Airport 10:37+9 min+9 min
Sat 17 OctSchiphol Airport 10:310 min—
Fri 16 OctSchiphol Airport 10:31No data—
Thu 15 OctHoorn 10:58No data—
Wed 14 OctSchiphol Airport 10:31No data—
Tue 13 OctSchiphol Airport 10:310 min—
Mon 12 OctSchiphol Airport 10:31No data—
Sun 11 OctSchiphol Airport 10:310 min—
Sat 10 OctSchiphol Airport 10:32+4 min+4 min
Fri 9 OctSchiphol Airport 10:32+1 min+1 min
Thu 8 OctSchiphol Airport 10:31Partial coverage0 min—
Wed 7 OctSchiphol Airport 10:37Partial coverage0 min—
Tue 6 OctSchiphol Airport 10:35Partial coverage+4 min+4 min
Mon 5 OctZaandam 10:06No data—
Sun 4 OctSassenheim 10:47No data—
Sat 3 OctSchiphol Airport 10:25No data—
Fri 2 OctSchiphol Airport 10:33No data—
Thu 1 OctSchiphol Airport 10:31No data—
Wed 30 SeptSchiphol Airport 10:33No data—
Tue 29 SeptSchiphol Airport 10:31No data—
Mon 28 SeptSchiphol Airport 10:45No data—
Sun 27 SeptZaandam 10:05No data—
Sat 26 SeptSchiphol Airport 10:31No data—
Fri 25 SeptSchiphol Airport 10:31No data—
Thu 24 SeptSchiphol Airport 10:31No data—
Wed 23 SeptSchiphol Airport 10:31No data—