Train Arriva 37246 Harlingen Haven – Leeuwarden

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

Running now · updated 12:33

Heading to Leeuwarden 0 min

Estimated arrival at Leeuwarden 12:40 · 76 km/h

  1. Harlingen Haven12:11
  2. Harlingen12:14
  3. Franeker12:22
  4. Dronryp12:29
  5. Deinum12:35
  6. Leeuwarden12:40

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 11 runs arrived on time.

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%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 74 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

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

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

On-time by weekday

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

Stops and timetable

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

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