Train Arriva 37255 Leeuwarden – Harlingen Haven

Leeuwarden 17:50 → Harlingen Haven 18:18 Daily 0 h 28 min · 6 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 17:50 from Leeuwarden · Sat 7 Nov

Next departure 17:50 today · Leeuwarden
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 20 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 1 full · 10 partial · 77 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
17:50on time on time
17:54— —
17:59 / 18:00— —
18:05 / 18:06— —
18:14 / 18:15— —
18: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
Fri 6 NovHarlingen 18:29Partial coverage+1 min—
Thu 5 NovFraneker 18:19No data—
Wed 4 NovHarlingen 18:29Partial coverage0 min—
Tue 3 NovFraneker 18:19No data—
Mon 2 NovFraneker 18:19No data—
Sun 1 NovHarlingen 18:29No data—
Sat 31 OctHarlingen 18:29No data—
Fri 30 OctHarlingen 18:29No data—
Thu 29 OctDronryp 18:14No data—
Wed 28 OctFraneker 18:20Partial coverage0 min—
Tue 27 OctDronryp 18:14No data—
Mon 26 OctFraneker 18:20Partial coverage0 min—
Sun 25 OctHarlingen 18:29No data—
Sat 24 OctHarlingen 18:29No data—
Fri 23 OctHarlingen 18:29No data—
Thu 22 OctHarlingen 18:29No data—
Wed 21 OctHarlingen 18:29No data—
Tue 20 OctHarlingen 18:29Partial coverage0 min—
Mon 19 OctHarlingen 18:29No data—
Sun 18 OctHarlingen 18:29Partial coverage0 min—
Sat 17 OctHarlingen 18:29No data—
Fri 16 OctHarlingen 18:29No data—
Thu 15 OctHarlingen 18:29No data—
Wed 14 OctHarlingen 18:30No data—
Tue 13 OctHarlingen 18:29No data—
Mon 12 OctHarlingen 18:29Partial coverage0 min—
Sun 11 OctHarlingen 18:29Partial coverage0 min—
Sat 10 OctHarlingen 18:29Partial coverage0 min—
Fri 9 OctHarlingen 18:29No data—
Thu 8 OctDronryp 18:140 min—