Train Arriva 38057 Leeuwarden – Sneek

Leeuwarden 18:07 → Sneek 18:24 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 3 stops Arriva

✓ Today’s run finished

Today, last fix heading to Leeuwarden at 18:19 No data

  1. Leeuwarden18:07
  2. Sneek Noord18:21
  3. Sneek18:24

Next service: tomorrow 18:07 from Leeuwarden · Fri 6 Nov

Next departure 18:07 tomorrow · Leeuwarden
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 0 full · 4 partial · 10 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 0 full · 5 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Sneek, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +4 min · last fix heading to Sneek Noord +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 20% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 5 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
18:07on time +1 min
18:21 / 18:22— —
18:24— —

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 NovLeeuwarden 18:19No data—
Wed 4 NovLeeuwarden 18:19No data—
Tue 3 NovLeeuwarden 18:19No data—
Mon 2 NovLeeuwarden 18:19No data—
Fri 30 OctSneek Noord 18:36No data—
Wed 28 OctLeeuwarden 18:21Partial coverage0 min—
Mon 26 OctLeeuwarden 18:21No data—
Fri 23 OctSneek Noord 18:36No data—
Thu 22 OctSneek Noord 18:36No data—
Wed 21 OctSneek Noord 18:34No data—
Tue 20 OctSneek Noord 18:36Partial coverage0 min—
Mon 19 OctSneek Noord 18:36Partial coverage0 min—
Fri 9 OctSneek Noord 18:36Partial coverage+4 min+4 min
Wed 7 OctLeeuwarden 18:21No data—
Mon 5 OctLeeuwarden 18:21Partial coverage0 min—
Fri 2 OctSneek Noord 18:36No data—
Wed 30 SeptLeeuwarden 18:18No data—
Tue 29 SeptLeeuwarden 18:21No data—
Fri 25 SeptSneek Noord 18:36No data—
Wed 23 SeptLeeuwarden 18:21No data—
Mon 21 SeptLeeuwarden 18:21No data—
Fri 18 SeptSneek Noord 18:36No data—
Thu 17 SeptLeeuwarden 18:21No data—
Tue 15 SeptLeeuwarden 18:21No data—
Mon 14 SeptLeeuwarden 18:21No data—
Fri 11 SeptSneek Noord 18:36No data—
Thu 10 SeptLeeuwarden 18:22No data—
Tue 8 SeptLeeuwarden 18:21No data—
Mon 7 SeptSneek Noord 18:36No data—
Fri 4 SeptSneek Noord 18:36No data—