Train Arriva 38049 Leeuwarden – Sneek

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

✓ Today’s run finished

Today, last fix heading to Sneek Noord at 16:39 No data

  1. Leeuwarden16:07
  2. Sneek Noord16:21
  3. Sneek16:24

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

Next departure 16:07 tomorrow · Leeuwarden
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 10 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 48 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: +1 min

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

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 100% · 8
  • 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=1
  • 100% W n=3
  • 100% T n=2
  • — F n=0
  • — 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
16:07on time on time
16:21 / 16:22— —
16: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 NovSneek Noord 16:39No data—
Wed 4 NovSneek Noord 16:37Partial coverage+1 min—
Tue 3 NovSneek Noord 16:34No data—
Mon 2 NovSneek Noord 16:37No data—
Fri 30 OctSneek Noord 16:36No data—
Thu 29 OctSneek Noord 16:36Partial coverage0 min—
Wed 28 OctSneek Noord 16:36Partial coverage0 min—
Tue 27 OctSneek Noord 16:37No data—
Mon 26 OctSneek Noord 16:36No data—
Fri 23 OctSneek Noord 16:38No data—
Thu 22 OctSneek Noord 16:38No data—
Wed 21 OctSneek Noord 16:36No data—
Tue 20 OctSneek Noord 16:38Partial coverage0 min—
Mon 19 OctSneek Noord 16:37Partial coverage0 min—
Fri 9 OctSneek Noord 16:36No data—
Thu 8 OctSneek Noord 16:37Partial coverage+1 min+1 min
Wed 7 OctSneek Noord 16:36Partial coverage0 min—
Tue 6 OctSneek Noord 16:36No data—
Mon 5 OctSneek Noord 16:38Partial coverage0 min—
Fri 2 OctSneek Noord 16:41No data—
Thu 1 OctSneek Noord 16:36No data—
Wed 30 SeptSneek Noord 16:36No data—
Tue 29 SeptSneek Noord 16:36No data—
Mon 28 SeptSneek Noord 16:37No data—
Fri 25 SeptSneek Noord 16:36No data—
Thu 24 SeptSneek Noord 16:36No data—
Wed 23 SeptSneek Noord 16:36No data—
Tue 22 SeptSneek Noord 16:36No data—
Mon 21 SeptSneek Noord 16:37No data—
Fri 18 SeptSneek Noord 16:37No data—