Train NS 4010 Breukelen – Wormerveer

Breukelen 05:41 → Wormerveer 06:34 Mon, Tue, Wed, Thu, Fri, Sat 0 h 53 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Zaandijk Zaanse Schans at 06:49 +5 min

  1. Breukelen05:41
  2. Amsterdam Holendrecht05:53
  3. Duivendrecht05:58
  4. Amsterdam Muiderpoort06:06
  5. Amsterdam Sloterdijk06:18
  6. Zaandijk Zaanse Schans06:30
  7. Wormerveer06:34

Next service: tomorrow 05:41 from Breukelen · Thu 15 Oct

Full trip card
Next departure 05:41 tomorrow · Breukelen
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 7 full · 1 partial · 17 no data
On-time · 90 days
75%
6/8 runs under 3 min
RT coverage: 7 full · 1 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Wormerveer, 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 13 Oct Max en route +16 min · last fix heading to Zaandijk Zaanse Schans +16 min
  • Wed 14 Oct Max en route +5 min · last fix heading to Zaandijk Zaanse Schans +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 6
  • 3–10 min 13% · 1
  • 10–30 min 13% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 50% T n=2
  • 50% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=1
  • — S n=0

Stops and timetable

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

StopSched.
Breukelen
05:41
Abcoude
05:50
Amsterdam Holendrecht
05:53
Amsterdam Bijlmer ArenA
05:56
Duivendrecht
05:58
Amsterdam Amstel
06:02
Amsterdam Muiderpoort
06:06
Amsterdam Centraal
06:11 / 06:13
Amsterdam Sloterdijk
06:18
Zaandam
06:24
Koog aan de Zaan
06:28
Zaandijk Zaanse Schans
06:30
Wormerveer
06:34

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.

Recent runs

DateLast stopFinalMax
Wed 14 OctZaandijk Zaanse Schans 06:49Partial coverage+5 min+5 min
Tue 13 OctZaandijk Zaanse Schans 07:01+16 min+16 min
Mon 12 OctZaandijk Zaanse Schans 06:47+2 min+2 min
Sat 10 OctKrommenie-Assendelft 06:520 min—
Fri 9 OctKrommenie-Assendelft 06:510 min—
Thu 8 OctKrommenie-Assendelft 06:520 min—
Wed 7 OctKrommenie-Assendelft 06:520 min—
Tue 6 OctKrommenie-Assendelft 06:53+1 min+2 min
Mon 5 OctAmsterdam Muiderpoort 06:22No data—
Fri 2 OctKrommenie-Assendelft 06:53No data—
Thu 1 OctKrommenie-Assendelft 06:52No data—
Wed 30 SeptKrommenie-Assendelft 06:52No data—
Tue 29 SeptKrommenie-Assendelft 06:53No data—
Mon 28 SeptKrommenie-Assendelft 06:52No data—
Sat 26 SeptKrommenie-Assendelft 06:53No data—
Fri 25 SeptKrommenie-Assendelft 06:51No data—
Thu 24 SeptKrommenie-Assendelft 06:54No data—
Wed 23 SeptKrommenie-Assendelft 06:53No data—
Tue 22 SeptKrommenie-Assendelft 06:54No data—
Mon 21 SeptKrommenie-Assendelft 06:54No data—
Sat 19 SeptKrommenie-Assendelft 06:52No data—
Fri 18 SeptKrommenie-Assendelft 06:52No data—
Thu 17 SeptKrommenie-Assendelft 06:51No data—
Wed 16 SeptKrommenie-Assendelft 06:51No data—
Tue 15 SeptKrommenie-Assendelft 06:52No data—
Mon 14 SeptKrommenie-Assendelft 06:53No data—
Sat 12 SeptKrommenie-Assendelft 06:53No data—
Fri 11 SeptKrommenie-Assendelft 06:53No data—
Thu 10 SeptKrommenie-Assendelft 06:53No data—
Tue 8 SeptKrommenie-Assendelft 06:52No data—