Train Arriva 38032 Sneek – Leeuwarden

Sneek 09:06 → Leeuwarden 09:23 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 3 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 09:06 from Sneek · Thu 5 Nov

Next departure 09:06 today · Sneek
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 9 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 49 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 +7 min · last fix heading to Sneek Noord +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=2
  • 50% T n=2
  • 100% 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, 8 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:06on time +1 min
09:08— —
09:23— —

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
Wed 4 NovSneek Noord 09:24Partial coverage+1 min—
Tue 3 NovSneek Noord 09:24No data—
Mon 2 NovSneek Noord 09:24No data—
Fri 30 OctSneek Noord 09:24No data—
Thu 29 OctSneek Noord 09:23Partial coverage0 min—
Wed 28 OctSneek Noord 09:23Partial coverage0 min—
Tue 27 OctSneek Noord 09:22No data—
Mon 26 OctSneek Noord 09:31No data—
Fri 23 OctSneek Noord 09:24No data—
Thu 22 OctSneek Noord 09:24No data—
Wed 21 OctSneek Noord 09:26No data—
Tue 20 OctSneek Noord 09:25Partial coverage0 min—
Mon 19 OctSneek Noord 09:25Partial coverage0 min—
Fri 9 OctSneek Noord 09:23Partial coverage0 min—
Thu 8 OctSneek Noord 09:28Partial coverage+7 min+7 min
Wed 7 OctSneek Noord 09:23No data—
Tue 6 OctSneek Noord 09:24Partial coverage+3 min+3 min
Mon 5 OctSneek Noord 09:25No data—
Fri 2 OctSneek Noord 09:26No data—
Thu 1 OctSneek Noord 09:24No data—
Wed 30 SeptSneek Noord 09:29No data—
Tue 29 SeptSneek Noord 09:23No data—
Mon 28 SeptSneek Noord 09:24No data—
Fri 25 SeptSneek Noord 09:23No data—
Thu 24 SeptSneek Noord 09:23No data—
Wed 23 SeptSneek Noord 09:23No data—
Tue 22 SeptSneek Noord 09:23No data—
Mon 21 SeptSneek Noord 09:23No data—
Fri 18 SeptSneek Noord 09:23No data—
Thu 17 SeptSneek Noord 09:25No data—