Train NS 9090 Leeuwarden – Zwolle

Leeuwarden 23:46 → Zwolle 00:48 Daily 1 h 02 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:46 from Leeuwarden · Fri 6 Nov

Next departure 23:46 today · Leeuwarden
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 18 full · 2 partial · 5 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 20 full · 3 partial · 17 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

  • Mon 19 Oct Max en route +5 min · last fix heading to — +5 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

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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 10
23:46on time on time
23:55≈ on time ≈ on time
23:59≈ on time ≈ on time
00:06≈ on time ≈ on time
00:13≈ on time ≈ on time
00:21 / 00:24≈ on time ≈ on time
00:33≈ on time ≈ on time
00:48on 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— 00:49No data—
Wed 4 Nov— 00:490 min—
Mon 2 Nov— 00:490 min—
Sun 1 NovMeppel 00:490 min—
Fri 30 Oct— 01:09No data—
Thu 29 Oct— 00:52+2 min+3 min
Wed 28 Oct— 00:490 min—
Tue 27 Oct— 00:500 min—
Mon 26 Oct— 00:490 min—
Fri 23 Oct— 01:100 min—
Thu 22 Oct— 00:490 min—
Wed 21 Oct— 00:490 min—
Tue 20 Oct— 00:15No data—
Mon 19 Oct— 00:59+5 min+5 min
Sun 18 OctMeppel 00:50Partial coverage0 min—
Sat 17 OctLeeuwarden 01:08No data—
Fri 16 Oct— 01:090 min—
Thu 15 Oct— 00:540 min—
Wed 14 Oct— 00:490 min—
Tue 13 Oct— 00:50No data—
Mon 12 Oct— 00:490 min—
Sun 11 OctMeppel 00:49Partial coverage0 min—
Sat 10 Oct— 01:090 min—
Fri 9 Oct— 00:330 min—
Thu 8 Oct— 00:490 min—
Wed 7 Oct— 00:490 min—
Tue 6 Oct— 00:500 min—
Mon 5 OctHeerenveen 00:49Partial coverage0 min—
Sun 4 OctMeppel 00:47No data—
Sat 3 OctMeppel 00:31No data—