Train Arriva 37258 Harlingen Haven – Leeuwarden

Harlingen Haven 15:11 → Leeuwarden 15:40 Daily 0 h 29 min · 6 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:11 from Harlingen Haven · Thu 5 Nov

Next departure 15:11 today · Harlingen Haven
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%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 78 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: 0 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

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=2
  • 100% W n=3
  • 100% T n=1
  • 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, 10 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
15:11on time on time
15:14 / 15:15— —
15:22 / 15:23— —
15:29 / 15:30— —
15:35— —
15:40— —

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
Wed 4 NovDeinum 15:49Partial coverage0 min—
Tue 3 NovDeinum 15:49No data—
Mon 2 NovDeinum 15:49No data—
Sun 1 NovDeinum 15:50No data—
Sat 31 OctDeinum 15:49No data—
Fri 30 OctDeinum 15:49No data—
Thu 29 OctDeinum 15:49No data—
Wed 28 OctDeinum 15:50Partial coverage0 min—
Tue 27 OctDeinum 15:50Partial coverage0 min—
Mon 26 OctDeinum 15:50No data—
Sun 25 OctDeinum 15:49No data—
Sat 24 OctDeinum 15:49No data—
Fri 23 OctDeinum 15:49No data—
Thu 22 OctDeinum 15:49No data—
Wed 21 OctDeinum 15:50No data—
Tue 20 OctDeinum 15:49Partial coverage0 min—
Mon 19 OctDeinum 15:50Partial coverage0 min—
Sun 18 OctDeinum 15:50No data—
Sat 17 OctDeinum 15:49No data—
Fri 16 OctDeinum 15:50No data—
Thu 15 OctDeinum 15:50No data—
Wed 14 OctDeinum 15:50No data—
Tue 13 OctDeinum 15:52No data—
Mon 12 OctDeinum 15:49Partial coverage0 min—
Sun 11 OctDeinum 15:49No data—
Sat 10 OctDeinum 15:49No data—
Fri 9 OctDeinum 15:49Partial coverage0 min—
Thu 8 OctDeinum 15:49Partial coverage0 min—
Wed 7 OctDeinum 15:50Partial coverage+1 min+1 min
Tue 6 OctDeinum 15:50No data—