Train Arriva 37019 Leeuwarden → Sneek

Leeuwarden 08:53 → Sneek 09:12 Mon, Tue, Wed, Thu, Fri, Sat 0 h 19 min · 4 stops Arriva

Arriva 37019 Leeuwarden–Sneek: final delay under 3 min on 15 of its 17 runs with data in the last 30 days (88%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 23:21 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Sneek Noord at 09:24 +1 min

  1. Leeuwarden08:53
  2. Mantgum09:00
  3. Sneek Noord09:09
  4. Sneek09:12

Next service: Monday 08:53 from Leeuwarden · Mon 23 Nov

Next departure 08:53 Monday · Leeuwarden
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 15 full · 2 partial · 9 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 18 full · 2 partial · 50 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=4
  • 75% T n=4
  • 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, 20 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:53on time on time
09:00≈ on time ≈ +1 min
09:09≈ +1 min ≈ +3 min
09:12+1 min +3 min

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
Sat 21 NovSneek Noord 09:24Partial coverage+1 min—
Fri 20 NovSneek Noord 09:24+2 min+2 min
Thu 19 NovSneek Noord 09:24+2 min+2 min
Wed 18 NovSneek Noord 09:24+1 min+1 min
Tue 17 NovSneek Noord 09:24+2 min+2 min
Mon 16 NovSneek Noord 09:24+3 min+3 min
Sat 14 NovSneek Noord 09:24Partial coverage+1 min—
Fri 13 NovSneek Noord 09:27+4 min+4 min
Thu 12 NovSneek Noord 09:230 min—
Wed 11 NovSneek Noord 09:240 min—
Tue 10 NovSneek Noord 09:24+2 min+2 min
Mon 9 NovSneek Noord 09:230 min—
Sat 7 NovSneek Noord 09:23No data—
Fri 6 NovSneek Noord 09:24No data—
Thu 5 NovSneek Noord 09:24No data—
Wed 4 NovSneek Noord 09:24+1 min—
Tue 3 NovSneek Noord 09:240 min—
Mon 2 NovSneek Noord 09:240 min—
Sat 31 OctSneek Noord 09:23No data—
Fri 30 OctSneek Noord 09:24No data—
Thu 29 OctSneek Noord 09:230 min—
Wed 28 OctSneek Noord 09:240 min—
Tue 27 OctSneek Noord 09:24No data—
Mon 26 OctSneek Noord 09:32No data—
Sat 24 OctSneek Noord 09:24No data—
Fri 23 OctSneek Noord 09:24No data—
Thu 22 OctSneek Noord 09:24No data—
Wed 21 OctSneek Noord 09:27No data—
Tue 20 OctSneek Noord 09:26No data—
Mon 19 OctSneek Noord 09:260 min—