Train NS 4169 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 17:54 → Hoofddorp 18:52 Daily 0 h 58 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 17:54 from Hoorn Kersenboogerd · Thu 19 Nov

Next departure 17:54 today · Hoorn Kersenboogerd
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 9 full · 12 partial · 8 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 15 full · 17 partial · 56 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

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

  • Early 0% · 0
  • On time 100% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
17:54on time on time
17:57 / 17:58≈ on time ≈ on time
18:09≈ on time ≈ on time
18:12≈ on time ≈ on time
18:15≈ on time ≈ on time
18:21≈ on time ≈ on time
18:25≈ on time ≈ on time
18:31 / 18:36≈ on time ≈ on time
18:40≈ on time ≈ on time
18:46 / 18:47≈ on time ≈ on time
18:52on time on time

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
Wed 18 NovAmsterdam Lelylaan 18:54Partial coverage0 min—
Tue 17 NovZaandam Kogerveld 18:53Partial coverage0 min—
Mon 16 NovZaandam 18:39Partial coverage0 min—
Sun 15 NovSchiphol Airport 19:020 min—
Sat 14 NovSchiphol Airport 18:590 min—
Fri 13 NovSchiphol Airport 18:590 min—
Thu 12 NovZaandam Kogerveld 19:04Partial coverage+2 min+2 min
Wed 11 NovPurmerend 18:53Partial coverage0 min—
Tue 10 NovZaandam Kogerveld 18:59Partial coverage+2 min+3 min
Mon 9 NovPurmerend 18:54Partial coverage+1 min+1 min
Sun 8 NovSchiphol Airport 18:590 min—
Sat 7 NovZaandam 18:340 min—
Fri 6 NovSchiphol Airport 18:590 min—
Thu 5 NovPurmerend 18:53No data—
Wed 4 NovPurmerend Weidevenne 18:54No data—
Tue 3 NovPurmerend 18:53Partial coverage0 min—
Mon 2 NovPurmerend Overwhere 18:53Partial coverage0 min—
Sun 1 NovSchiphol Airport 18:59No data—
Sat 31 OctSchiphol Airport 19:010 min—
Fri 30 OctSchiphol Airport 19:01No data—
Thu 29 OctHoorn 18:54Partial coverage0 min—
Wed 28 OctPurmerend 19:06Partial coverage0 min—
Tue 27 OctHoorn 18:58No data—
Mon 26 OctPurmerend Overwhere 18:53Partial coverage0 min—
Sun 25 OctSchiphol Airport 19:01No data—
Sat 24 OctSchiphol Airport 19:020 min—
Fri 23 OctSchiphol Airport 19:020 min—
Thu 22 OctAmsterdam Lelylaan 18:54No data—
Wed 21 OctAmsterdam Lelylaan 18:54No data—
Tue 20 OctAmsterdam Lelylaan 18:54No data—