Train NS 4148 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 15:08 → Hoorn Kersenboogerd 16:07 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 15:08 from Hoofddorp · Wed 18 Nov

Next departure 15:08 today · Hoofddorp
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 11 full · 9 partial · 9 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 17 full · 13 partial · 58 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 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

  • Mon 12 Oct Max en route +10 min · last fix heading to Hoorn +10 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 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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