Train NS 4125 Hoorn Kersenboogerd – Hoofddorp

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 06:54 from Hoorn Kersenboogerd · Fri 6 Nov

Next departure 06:54 today · Hoorn Kersenboogerd
On-time · 30 days
93%
25/27 runs under 3 min
RT coverage: 11 full · 16 partial · 2 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 11 full · 18 partial · 59 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: +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

Worst days

  • Mon 26 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min
  • Sat 17 Oct Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
06:54on time on time
06:57 / 06:58≈ on time ≈ on time
07:09≈ on time ≈ on time
07:12≈ on time ≈ on time
07:15≈ on time ≈ +1 min
07:21≈ on time ≈ +1 min
07:25≈ on time ≈ +1 min
07:31 / 07:36≈ on time ≈ +1 min
07:40≈ on time ≈ +1 min
07:46 / 07:47≈ on time ≈ +1 min
07:52on 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 5 NovSchiphol Airport 08:02Partial coverage0 min—
Wed 4 NovSchiphol Airport 07:59Partial coverage0 min—
Tue 3 NovSchiphol Airport 07:59Partial coverage0 min—
Mon 2 NovSchiphol Airport 07:59No data—
Sun 1 NovSchiphol Airport 07:570 min—
Sat 31 OctSchiphol Airport 07:570 min—
Fri 30 OctSchiphol Airport 08:010 min—
Thu 29 OctSchiphol Airport 08:01Partial coverage0 min—
Wed 28 OctSchiphol Airport 08:02Partial coverage0 min—
Tue 27 OctSchiphol Airport 08:02Partial coverage0 min—
Mon 26 OctSchiphol Airport 08:05Partial coverage+5 min+5 min
Sun 25 OctSchiphol Airport 07:57No data—
Sat 24 OctSchiphol Airport 07:57+1 min+1 min
Fri 23 OctSchiphol Airport 08:010 min—
Thu 22 OctSchiphol Airport 08:02Partial coverage0 min—
Wed 21 OctSchiphol Airport 08:01Partial coverage0 min—
Tue 20 OctSchiphol Airport 08:01Partial coverage0 min—
Mon 19 OctSchiphol Airport 08:01Partial coverage0 min—
Sun 18 OctSchiphol Airport 07:58+2 min+2 min
Sat 17 OctSchiphol Airport 07:57+3 min+3 min
Fri 16 OctSchiphol Airport 08:050 min—
Thu 15 OctSchiphol Airport 08:02Partial coverage0 min—
Wed 14 OctSchiphol Airport 08:01Partial coverage0 min—
Tue 13 OctSchiphol Airport 08:02Partial coverage0 min—
Mon 12 OctSchiphol Airport 08:01Partial coverage0 min—
Sun 11 OctSchiphol Airport 07:57+1 min+1 min
Sat 10 OctSchiphol Airport 07:570 min—
Fri 9 OctSchiphol Airport 08:010 min—
Thu 8 OctSchiphol Airport 08:02Partial coverage0 min—
Wed 7 OctSchiphol Airport 08:01Partial coverage0 min—