Train NS 888 Leeuwarden – Zwolle

Leeuwarden 23:16 → Zwolle 00:11 Mon, Tue, Wed, Thu, Sun 0 h 55 min · 5 stops NS (Nederlandse Spoorwegen)

Running now · updated 23:50

Heading to Zwolle 0 min

Estimated arrival at Zwolle 00:11 · 130 km/h

  1. Leeuwarden23:16
  2. Heerenveen23:32
  3. Steenwijk23:46
  4. Meppel23:56
  5. Zwolle00:11

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 2 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Zwolle, 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 29 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 80% T n=5
  • — F n=0
  • 100% S n=1
  • 100% S n=3

Stops and timetable

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

Last 90 days, 23 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 10Today
23:16on time on time
23:32≈ on time ≈ on time
23:46≈ on time ≈ on time
23:56≈ on time ≈ on time
00:11on time on time

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 Nov— 23:490 min—
Wed 4 Nov— 00:130 min—
Tue 3 Nov— 00:130 min—
Mon 2 Nov— 00:120 min—
Sun 1 NovMeppel 00:130 min—
Thu 29 Oct— 00:25+6 min+6 min
Wed 28 Oct— 00:120 min—
Tue 27 Oct— 00:120 min—
Mon 26 Oct— 00:120 min—
Sun 25 OctMeppel 00:15No data—
Sat 24 Oct— 00:130 min—
Thu 22 Oct— 00:120 min—
Wed 21 Oct— 00:120 min—
Tue 20 Oct— 00:15No data—
Mon 19 Oct— 00:100 min—
Sun 18 OctMeppel 00:120 min—
Thu 15 Oct— 00:140 min—
Wed 14 Oct— 00:120 min—
Tue 13 Oct— 00:130 min—
Mon 12 Oct— 00:120 min—
Sun 11 OctMeppel 00:120 min—
Thu 8 Oct— 00:120 min—
Wed 7 Oct— 00:120 min—
Tue 6 Oct— 00:120 min—
Mon 5 OctMeppel 00:120 min—
Sun 4 OctMeppel 00:10No data—
Sun 27 SeptMeppel 00:10No data—
Sun 20 SeptMeppel 00:11No data—
Sun 13 SeptMeppel 00:10No data—
Sun 30 AugMeppel 00:10No data—