Train Arriva 37028 Sneek – Leeuwarden

Sneek 07:48 → Leeuwarden 08:08 Sun 0 h 20 min · 4 stops Arriva

It does not run today

Last recorded run: Sunday 25 October No data

Next service: Sunday 07:48 from Sneek · Sun 1 Nov

Next departure 07:48 Sunday · Sneek
On-time · 30 days
—
Too little data (1/3 runs with data)
RT coverage: 0 full · 1 partial · 2 no data
On-time · 90 days
—
Too little data (1/12 runs with data)
RT coverage: 0 full · 1 partial · 11 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 1
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
Sneek
07:48
Sneek Noord
07:51
Mantgum
07:59 / 08:00
Leeuwarden
08:08

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.

Recent runs

DateLast stopFinalMax
Sun 25 OctMantgum 08:14No data—
Sun 18 OctMantgum 08:14Partial coverage+1 min+1 min
Sun 4 OctMantgum 08:14No data—
Sun 27 SeptMantgum 08:14No data—
Sun 20 SeptMantgum 08:14No data—
Sun 13 SeptMantgum 08:14No data—
Sun 6 SeptMantgum 08:14No data—
Sun 30 AugMantgum 08:14No data—
Sun 23 AugMantgum 08:15No data—
Sun 16 AugMantgum 08:14No data—
Sun 9 AugMantgum 08:14No data—
Sun 2 AugMantgum 08:14No data—