Train NS 588 Groningen – Zwolle

Groningen 23:18 → Zwolle 00:14 Daily 0 h 56 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 23:18 from Groningen · Thu 5 Nov

Next departure 23:18 today · Groningen
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 2 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 partial · 14 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 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

  • Sun 1 Nov Max en route +9 min · last fix heading to Assen +9 min
  • Mon 19 Oct Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 27 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:18on time on time
23:35≈ on time ≈ on time
00:14on time +1 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
Wed 4 Nov— 00:140 min—
Tue 3 Nov— 00:140 min—
Sun 1 NovAssen 00:34+9 min+9 min
Sat 31 OctGroningen 00:160 min—
Fri 30 Oct— 00:160 min—
Thu 29 Oct— 00:150 min—
Wed 28 Oct— 00:150 min—
Tue 27 Oct— 00:160 min—
Mon 26 Oct— 00:160 min—
Sun 25 OctAssen 00:160 min—
Sat 24 Oct— 00:150 min—
Thu 22 Oct— 00:320 min—
Wed 21 Oct— 00:150 min—
Tue 20 Oct— 00:17No data—
Mon 19 Oct— 00:02+8 min+8 min
Sun 18 OctAssen 00:17+1 min+2 min
Sat 17 OctAssen 00:180 min—
Fri 16 Oct— 00:150 min—
Thu 15 Oct— 00:160 min—
Wed 14 Oct— 00:150 min—
Tue 13 Oct— 00:20No data—
Mon 12 Oct— 00:150 min—
Sun 11 OctAssen 00:150 min—
Sat 10 Oct— 00:440 min+13 min
Fri 9 Oct— 00:150 min—
Thu 8 Oct— 00:170 min+2 min
Wed 7 Oct— 00:150 min—
Tue 6 Oct— 00:150 min—
Mon 5 OctAssen 00:150 min—
Sun 4 OctAssen 23:50No data—