Train Arriva 37224 Harlingen Haven – Leeuwarden

Harlingen Haven 06:41 → Leeuwarden 07:11 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to Deinum at 07:19 No data

  1. Harlingen Haven06:41
  2. Harlingen06:44
  3. Franeker06:52
  4. Dronryp06:59
  5. Deinum07:05
  6. Leeuwarden07:11

Next service: Monday 06:41 from Harlingen Haven · Mon 9 Nov

Next departure 06:41 Monday · Harlingen Haven
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 7 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 46 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 Leeuwarden, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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:41on time +1 min
06:44 / 06:45— —
06:52 / 06:53— —
06:59 / 07:00— —
07:05— —
07:11— —

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