Train NS 4144 Hoofddorp – Hoorn Kersenboogerd

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

✓ Today’s run finished

Today, last fix heading to Hoorn at 15:19 +1 min

  1. Hoofddorp14:08
  2. Amsterdam Lelylaan14:20
  3. Amsterdam Sloterdijk14:24
  4. Zaandam Kogerveld14:38
  5. Purmerend14:48
  6. Hoorn15:02
  7. Hoorn Kersenboogerd15:07

Next service: tomorrow 14:08 from Hoofddorp · Fri 20 Nov

Next departure 14:08 tomorrow · Hoofddorp
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 8 full · 12 partial · 10 no data
On-time · 90 days
83%
25/30 runs under 3 min
RT coverage: 14 full · 16 partial · 59 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: +3 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

Worst days

  • Thu 8 Oct Max en route +6 min · last fix heading to Hoorn +6 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Hoorn +5 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Hoorn +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Hoorn +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Hoorn +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 25
  • 3–10 min 17% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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