Train Arriva 37272 Harlingen Haven – Leeuwarden

Harlingen Haven 18:41 → Leeuwarden 19:10 Daily 0 h 29 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to Deinum at 19:19 0 min

  1. Harlingen Haven18:41
  2. Harlingen18:44
  3. Franeker18:52
  4. Dronryp18:59
  5. Deinum19:05
  6. Leeuwarden19:10

Next service: tomorrow 18:41 from Harlingen Haven · Sun 8 Nov

Next departure 18:41 tomorrow · Harlingen Haven
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 11 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 45 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

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

  • Early 0% · 0
  • On time 100% · 7
  • 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=1
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 7 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
18:41on time on time
18:44 / 18:45— —
18:52 / 18:53— —
18:59 / 19:00— —
19:05— —
19:10— —

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
Sat 7 NovDeinum 19:19Partial coverage0 min+1 min
Fri 6 NovHarlingen 18:59No data—
Sun 1 NovDeinum 19:19No data—
Sat 31 OctDeinum 19:20Partial coverage+1 min+1 min
Fri 30 OctFraneker 19:07No data—
Sun 25 OctDeinum 19:20No data—
Sat 24 OctDeinum 19:20No data—
Fri 23 OctDeinum 19:15No data—
Thu 22 OctHarlingen 18:59No data—
Tue 20 OctHarlingen 18:50Partial coverage0 min—
Mon 19 OctHarlingen Haven 18:55No data—
Sun 18 OctDeinum 19:20Partial coverage+1 min+1 min
Sat 17 OctDeinum 19:19No data—
Fri 16 OctDeinum 19:19No data—
Wed 14 OctDeinum 19:19No data—
Mon 12 OctHarlingen 18:59Partial coverage0 min—
Sun 11 OctDeinum 19:20Partial coverage+1 min+1 min
Sat 10 OctDeinum 19:20Partial coverage+1 min+1 min
Sun 4 OctDeinum 19:19No data—
Sat 3 OctDeinum 19:19No data—
Fri 2 OctHarlingen 18:59No data—
Sun 27 SeptDeinum 19:20No data—
Sat 26 SeptDeinum 19:19No data—
Sun 20 SeptDeinum 19:20No data—
Sat 19 SeptDeinum 19:19No data—
Fri 18 SeptHarlingen 18:59No data—
Sun 13 SeptDeinum 19:20No data—
Sat 12 SeptDeinum 19:19No data—
Fri 11 SeptHarlingen 18:59No data—
Sun 6 SeptDeinum 19:20No data—