Train Arriva 37211 Leeuwarden – Harlingen Haven

Leeuwarden 06:50 → Harlingen Haven 07:18 Mon, Tue, Wed, Thu, Fri, Sat 0 h 28 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to Harlingen at 07:29 No data

  1. Leeuwarden06:50
  2. Deinum06:54
  3. Dronryp06:59
  4. Franeker07:05
  5. Harlingen07:14
  6. Harlingen Haven07:18

Next service: tomorrow 06:50 from Leeuwarden · Fri 6 Nov

Next departure 06:50 tomorrow · Leeuwarden
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 14 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 64 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 Harlingen Haven, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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:50on time on time
06:54— —
06:59 / 07:00— —
07:05 / 07:06— —
07:14 / 07:15— —
07:18— —

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 NovHarlingen 07:29No data—
Wed 4 NovHarlingen 07:29Partial coverage+1 min—
Tue 3 NovHarlingen 07:29No data—
Mon 2 NovHarlingen 07:29No data—
Sat 31 OctHarlingen 07:29Partial coverage0 min—
Fri 30 OctHarlingen 07:29No data—
Thu 29 OctHarlingen 07:29No data—
Wed 28 OctHarlingen 07:29Partial coverage0 min—
Tue 27 OctHarlingen 07:29Partial coverage0 min—
Mon 26 OctHarlingen 07:29No data—
Sat 24 OctHarlingen 07:29No data—
Fri 23 OctHarlingen 07:29No data—
Thu 22 OctHarlingen 07:29No data—
Wed 21 OctHarlingen 07:29Partial coverage0 min—
Tue 20 OctHarlingen 07:29Partial coverage0 min—
Mon 19 OctHarlingen 07:29Partial coverage0 min—
Sat 17 OctHarlingen 07:29Partial coverage0 min—
Fri 16 OctHarlingen 07:29Partial coverage0 min—
Thu 15 OctHarlingen 07:29No data—
Wed 14 OctHarlingen 07:29No data—
Tue 13 OctHarlingen 07:29No data—
Mon 12 OctHarlingen 07:29No data—
Sat 10 OctHarlingen 07:29Partial coverage0 min—
Fri 9 OctHarlingen 07:29Partial coverage0 min—
Thu 8 OctHarlingen 07:30Partial coverage+1 min—
Wed 7 OctHarlingen 07:29No data—
Tue 6 OctHarlingen 07:29No data—
Mon 5 OctHarlingen 07:30No data—
Sat 3 OctHarlingen 07:29No data—
Fri 2 OctHarlingen 07:29No data—