Train Arriva 37217 Leeuwarden – Harlingen Haven

Leeuwarden 08:20 → Harlingen Haven 08:48 Daily 0 h 28 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to Harlingen at 08:59 No data

  1. Leeuwarden08:20
  2. Deinum08:24
  3. Dronryp08:29
  4. Franeker08:35
  5. Harlingen08:44
  6. Harlingen Haven08:48

Next service: tomorrow 08:20 from Leeuwarden · Fri 6 Nov

Next departure 08:20 tomorrow · Leeuwarden
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 20 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 78 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=2
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=1
  • 100% S n=2
  • — S n=0

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
08:20on time on time
08:24— —
08:29 / 08:30— —
08:35 / 08:36— —
08:44 / 08:45— —
08:48— —

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
Thu 5 NovHarlingen 08:59No data—
Wed 4 NovHarlingen 08:59Partial coverage0 min—
Tue 3 NovHarlingen 08:59Partial coverage0 min—
Mon 2 NovHarlingen 08:59Partial coverage0 min—
Sun 1 NovHarlingen 08:59No data—
Sat 31 OctHarlingen 08:59No data—
Fri 30 OctHarlingen 08:59No data—
Thu 29 OctHarlingen 08:59Partial coverage0 min—
Wed 28 OctHarlingen 08:59Partial coverage0 min—
Tue 27 OctHarlingen 09:00No data—
Mon 26 OctHarlingen 09:01No data—
Sun 25 OctHarlingen 08:59No data—
Sat 24 OctHarlingen 08:59Partial coverage0 min—
Fri 23 OctHarlingen 08:59No data—
Thu 22 OctHarlingen 08:59No data—
Wed 21 OctHarlingen 08:59No data—
Tue 20 OctHarlingen 08:59No data—
Mon 19 OctHarlingen 08:59Partial coverage0 min—
Sun 18 OctHarlingen 08:59No data—
Sat 17 OctHarlingen 08:59Partial coverage0 min—
Fri 16 OctHarlingen 08:59No data—
Thu 15 OctHarlingen 08:59No data—
Wed 14 OctHarlingen 08:59No data—
Tue 13 OctHarlingen 08:59No data—
Mon 12 OctHarlingen 08:59No data—
Sun 11 OctHarlingen 08:59No data—
Sat 10 OctHarlingen 08:59No data—
Fri 9 OctHarlingen 08:59Partial coverage0 min—
Thu 8 OctHarlingen 08:59Partial coverage0 min—
Wed 7 OctHarlingen 08:59No data—