Train NS 4184 Schiphol Airport – Hoorn

Schiphol Airport 00:19 → Hoorn 01:06 Daily 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:08 0 min

  1. Schiphol Airport00:19
  2. Amsterdam Lelylaan00:26
  3. Zaandam00:39
  4. Zaandam Kogerveld00:44
  5. Purmerend Weidevenne00:50
  6. Purmerend Overwhere00:55
  7. Hoorn01:06

Next service: tomorrow 00:19 from Schiphol Airport · Mon 9 Nov

Next departure 00:19 tomorrow · Schiphol Airport
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 9 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: +1 min

Last 30 days

Arrival delay at Hoorn, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 24 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 80% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 28 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
00:19on time on time
00:26≈ on time ≈ on time
00:30 / 00:33≈ on time ≈ on time
00:39≈ on time ≈ on time
00:44≈ on time ≈ on time
00:50≈ on time ≈ on time
00:53≈ on time ≈ on time
00:55≈ on time ≈ on time
01:06on 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
Sun 8 Nov— 01:080 min—
Sat 7 Nov— 01:08+2 min+2 min
Fri 6 Nov— 01:040 min—
Thu 5 Nov— 01:040 min—
Wed 4 Nov— 01:090 min—
Tue 3 Nov— 01:070 min—
Sun 1 NovPurmerend Overwhere 01:090 min—
Sat 31 Oct— 01:070 min—
Thu 29 Oct— 01:040 min—
Wed 28 Oct— 01:060 min—
Tue 27 Oct— 01:090 min—
Sun 25 OctPurmerend Overwhere 01:09No data—
Sat 24 Oct— 01:18+5 min+5 min
Fri 23 Oct— 01:040 min—
Thu 22 Oct— 01:040 min—
Wed 21 Oct— 01:110 min—
Tue 20 Oct— 01:500 min—
Sun 18 OctPurmerend Overwhere 01:100 min—
Sat 17 OctPurmerend Overwhere 01:080 min—
Fri 16 Oct— 01:150 min—
Thu 15 Oct— 01:070 min—
Wed 14 Oct— 01:070 min—
Tue 13 Oct— 01:100 min—
Sun 11 OctPurmerend Overwhere 01:260 min—
Sat 10 Oct— 01:12+2 min+2 min
Fri 9 Oct— 01:050 min—
Thu 8 Oct— 01:040 min—
Wed 7 Oct— 01:090 min—
Tue 6 Oct— 01:080 min—
Sun 4 OctPurmerend Overwhere 01:09No data—