Train NS 4189 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 22:48 → Hoofddorp 23: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 22:48 from Hoorn Kersenboogerd · Wed 18 Nov

Next departure 22:48 today · Hoorn Kersenboogerd
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 12 full · 6 partial · 9 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 23 full · 7 partial · 23 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: +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 +10 min · last fix heading to — +10 min
  • Thu 12 Nov Max en route +10 min · last fix heading to — +6 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 93% · 28
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=4
  • 50% T n=2
  • 100% F n=5
  • 100% 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, 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
22:48on time on time
22:52 / 22:53≈ on time ≈ on time
23:05≈ on time ≈ on time
23:08≈ on time ≈ on time
23:11≈ on time ≈ +1 min
23:17≈ on time ≈ +1 min
23:20≈ on time ≈ +1 min
23:26 / 23:31≈ on time ≈ +1 min
23:35≈ on time ≈ +1 min
23:41 / 23:43≈ on time ≈ +1 min
23:47on time +1 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— 23:480 min—
Mon 16 NovAmsterdam Sloterdijk 23:49Partial coverage0 min—
Sun 15 NovSchiphol Airport 23:57Partial coverage+1 min+1 min
Sat 14 NovHoorn 23:08Partial coverage0 min—
Fri 13 Nov— 23:480 min—
Thu 12 Nov— 00:07+6 min+10 min
Wed 11 Nov— 23:490 min—
Tue 10 Nov— 00:07+10 min+10 min
Mon 9 Nov— 23:490 min—
Sun 8 NovAmsterdam Lelylaan 23:490 min—
Sat 7 NovZaandam 23:48Partial coverage0 min—
Fri 6 Nov— 23:480 min—
Thu 5 Nov— 23:49No data—
Wed 4 Nov— 23:480 min—
Tue 3 Nov— 23:48No data—
Mon 2 Nov— 23:480 min+1 min
Sun 1 NovSchiphol Airport 23:57Partial coverage+1 min—
Sat 31 OctZaandam 23:48Partial coverage0 min—
Wed 28 Oct— 23:48No data—
Tue 27 Oct— 23:490 min—
Mon 26 Oct— 23:48No data—
Sun 25 OctSchiphol Airport 23:57No data—
Sat 24 Oct— 23:49No data—
Fri 23 Oct— 23:480 min—
Thu 22 Oct— 23:48No data—
Wed 21 Oct— 23:48No data—
Tue 20 Oct— 23:48No data—
Mon 19 Oct— 23:49No data—
Sun 18 OctSchiphol Airport 23:570 min—
Sat 17 OctSchiphol Airport 23:570 min—