Train NS 4181 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 20:48 → Hoofddorp 21:47 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 20:48 from Hoorn Kersenboogerd · Wed 18 Nov

Next departure 20:48 today · Hoorn Kersenboogerd
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 15 full · 4 partial · 9 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 26 full · 5 partial · 24 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: +2 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

  • Tue 10 Nov Max en route +3 min · last fix heading to — +3 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 67% T n=3
  • 100% W n=4
  • 100% T n=3
  • 100% F n=5
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 31 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
20:48on time on time
20:52 / 20:53≈ on time ≈ on time
21:05≈ on time ≈ on time
21:07≈ on time ≈ +1 min
21:10≈ on time ≈ +1 min
21:17≈ on time ≈ +1 min
21:20≈ on time ≈ +1 min
21:26 / 21:31≈ on time ≈ +1 min
21:35≈ on time ≈ +1 min
21:41 / 21:43≈ on time ≈ +1 min
21:47on 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
Tue 17 Nov— 21:480 min—
Mon 16 NovSchiphol Airport 21:48Partial coverage0 min—
Sun 15 NovSchiphol Airport 22:020 min—
Sat 14 NovSchiphol Airport 21:57Partial coverage0 min—
Fri 13 Nov— 21:480 min—
Thu 12 Nov— 21:49+1 min+1 min
Wed 11 Nov— 21:480 min—
Tue 10 Nov— 21:57+3 min+3 min
Mon 9 Nov— 21:480 min—
Sun 8 NovAmsterdam Lelylaan 21:49+2 min+2 min
Sat 7 NovSchiphol Airport 21:57Partial coverage+3 min+3 min
Fri 6 Nov— 21:480 min—
Thu 5 Nov— 21:49No data—
Wed 4 Nov— 21:490 min—
Tue 3 Nov— 21:27No data—
Mon 2 Nov— 21:48+1 min+1 min
Sun 1 NovSchiphol Airport 21:590 min—
Sat 31 OctSchiphol Airport 21:57No data—
Thu 29 Oct— 21:480 min—
Wed 28 Oct— 21:480 min—
Tue 27 Oct— 21:49No data—
Mon 26 Oct— 21:48No data—
Sun 25 OctSchiphol Airport 22:02No data—
Sat 24 OctSchiphol Airport 21:57Partial coverage0 min—
Fri 23 Oct— 21:490 min—
Thu 22 Oct— 21:49No data—
Wed 21 Oct— 21:48No data—
Tue 20 Oct— 21:10No data—
Mon 19 Oct— 21:480 min—
Sun 18 OctSchiphol Airport 22:010 min—