Train Arriva 37252 Harlingen Haven – Leeuwarden

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

✓ Today’s run finished

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

  1. Harlingen Haven13:41
  2. Harlingen13:44
  3. Franeker13:52
  4. Dronryp13:59
  5. Deinum14:05
  6. Leeuwarden14:10

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

Next departure 13:41 tomorrow · Harlingen Haven
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 19 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 75 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=4
  • 100% W n=2
  • 100% T n=2
  • — F n=0
  • 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, 14 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
13:41on time on time
13:44 / 13:45— —
13:52 / 13:53— —
13:59 / 14:00— —
14:05— —
14: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 14:19Partial coverage0 min—
Fri 6 NovDeinum 14:19No data—
Thu 5 NovDeinum 14:19No data—
Wed 4 NovDeinum 14:19Partial coverage0 min—
Tue 3 NovDeinum 14:19Partial coverage0 min—
Mon 2 NovDeinum 14:19Partial coverage0 min—
Sun 1 NovDeinum 14:20No data—
Sat 31 OctDeinum 14:19No data—
Fri 30 OctDeinum 14:19No data—
Thu 29 OctDeinum 14:19Partial coverage0 min—
Wed 28 OctDeinum 14:19Partial coverage0 min—
Tue 27 OctDeinum 14:19Partial coverage0 min—
Mon 26 OctDeinum 14:19No data—
Sun 25 OctDeinum 14:20No data—
Sat 24 OctDeinum 14:19Partial coverage0 min—
Fri 23 OctDeinum 14:19No data—
Thu 22 OctDeinum 14:19No data—
Wed 21 OctDeinum 14:19No data—
Tue 20 OctDeinum 14:20Partial coverage0 min—
Mon 19 OctDeinum 14:20Partial coverage0 min—
Sun 18 OctDeinum 14:20No data—
Sat 17 OctDeinum 14:19No data—
Fri 16 OctDeinum 14:19No data—
Thu 15 OctDeinum 14:19No data—
Wed 14 OctDeinum 14:19No data—
Tue 13 OctDeinum 14:19No data—
Mon 12 OctDeinum 14:19No data—
Sun 11 OctDeinum 14:19No data—
Sat 10 OctDeinum 14:20Partial coverage0 min—
Fri 9 OctDeinum 14:19No data—