Train NS 6159 Zwolle – Groningen

Zwolle 17:53 → Groningen 18:58 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:53 from Zwolle · Fri 6 Nov

Next departure 17:53 today · Zwolle
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 11 full · 9 partial · 9 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 11 full · 12 partial · 65 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: 0 min

Last 30 days

Arrival delay at Groningen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 7 Oct Max en route +6 min · last fix heading to Meppel +4 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=2
  • 75% W n=4
  • 100% T n=2
  • 100% F n=3
  • 100% S n=4
  • 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
17:53on time on time
18:08≈ on time ≈ on time
18:19≈ on time ≈ on time
18:28≈ on time ≈ on time
18:37≈ on time ≈ on time
18:49≈ on time ≈ on time
18:55≈ on time ≈ on time
18:58on 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 NovMeppel 19:14No data—
Wed 4 NovMeppel 18:59Partial coverage0 min—
Tue 3 NovMeppel 18:590 min—
Mon 2 NovMeppel 18:59Partial coverage0 min—
Sun 1 NovGroningen Europapark 19:090 min—
Sat 31 OctGroningen Europapark 19:090 min—
Fri 30 OctHaren 19:030 min—
Thu 29 OctZwolle 19:02Partial coverage0 min—
Wed 28 OctMeppel 18:59Partial coverage0 min—
Tue 27 OctZwolle 19:00No data—
Mon 26 OctMeppel 18:59Partial coverage0 min—
Sun 25 OctGroningen Europapark 19:09No data—
Sat 24 OctGroningen Europapark 19:090 min—
Fri 23 OctGroningen Europapark 19:09+1 min+2 min
Thu 22 OctAssen 19:17No data—
Wed 21 OctBeilen 19:00No data—
Tue 20 OctAssen 19:00No data—
Mon 19 OctAssen 18:51Partial coverage0 min—
Sun 18 OctGroningen Europapark 19:090 min—
Sat 17 OctGroningen Europapark 19:090 min—
Fri 16 OctGroningen Europapark 19:09No data—
Thu 15 OctBeilen 19:02No data—
Wed 14 OctGroningen Europapark 19:09Partial coverage0 min—
Tue 13 OctAssen 19:00No data—
Mon 12 OctAssen 18:59Partial coverage0 min—
Sun 11 OctGroningen Europapark 19:090 min—
Sat 10 OctGroningen Europapark 19:090 min+2 min
Fri 9 OctBeilen 18:590 min—
Thu 8 OctZwolle 19:00Partial coverage0 min—
Wed 7 OctMeppel 18:29Partial coverage+4 min+6 min