Train Arriva 37034 Sneek – Leeuwarden

Sneek 09:18 → Leeuwarden 09:38 Mon, Tue, Wed, Thu, Fri, Sat 0 h 20 min · 4 stops Arriva

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 09:18 from Sneek · Wed 18 Nov

Next departure 09:18 today · Sneek
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 0 full · 12 partial · 13 no data
On-time · 90 days
81%
13/16 runs under 3 min
RT coverage: 0 full · 16 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Thu 8 Oct Max en route +5 min · last fix heading to Mantgum +5 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Mantgum +4 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Mantgum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 13
  • 3–10 min 19% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=5
  • 100% W n=3
  • 0% T n=1
  • 50% F n=2
  • 100% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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
09:18on time on time
09:21— —
09:29 / 09:30— —
09:38— —

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 17 NovMantgum 09:44Partial coverage+1 min—
Mon 16 NovMantgum 09:48Partial coverage+4 min+4 min
Sat 14 NovMantgum 09:44Partial coverage0 min—
Fri 13 NovMantgum 09:48Partial coverage+3 min+5 min
Thu 12 NovMantgum 09:44Partial coverageNo data—
Wed 11 NovMantgum 09:44Partial coverage0 min—
Tue 10 NovMantgum 09:44Partial coverage+1 min+1 min
Mon 9 NovMantgum 09:44Partial coverage0 min—
Sat 7 NovMantgum 09:44No data—
Fri 6 NovMantgum 09:44No data—
Thu 5 NovMantgum 09:47No data—
Wed 4 NovMantgum 09:44Partial coverage0 min—
Tue 3 NovMantgum 09:44No data—
Mon 2 NovMantgum 09:44No data—
Sat 31 OctMantgum 09:44No data—
Fri 30 OctMantgum 09:45No data—
Thu 29 OctMantgum 09:44No data—
Wed 28 OctMantgum 09:44Partial coverage0 min—
Tue 27 OctMantgum 09:44Partial coverage0 min—
Mon 26 OctMantgum 09:49No data—
Sat 24 OctMantgum 09:45Partial coverage0 min—
Fri 23 OctMantgum 09:45No data—
Thu 22 OctMantgum 09:47No data—
Wed 21 OctMantgum 09:47No data—
Tue 20 OctMantgum 09:46Partial coverage0 min—
Mon 19 OctMantgum 09:46Partial coverage0 min—
Fri 9 OctMantgum 09:46Partial coverage0 min—
Thu 8 OctMantgum 09:51Partial coverage+5 min+5 min
Wed 7 OctMantgum 09:44Partial coverageNo data—
Tue 6 OctMantgum 09:45Partial coverage+2 min+2 min