Train NS 6158 Groningen – Zwolle

Groningen 15:32 → Zwolle 16:37 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 15:32 from Groningen · Sun 8 Nov

Next departure 15:32 today · Groningen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 12 full · 6 partial · 11 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 17 full · 6 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: +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

  • Thu 8 Oct Max en route +10 min · last fix heading to Meppel +10 min
  • Sat 10 Oct Max en route +8 min · last fix heading to Groningen +8 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 91% · 21
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=4
  • 67% T n=3
  • 100% F n=3
  • 75% 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
15:32on time on time
15:35≈ on time ≈ on time
15:39≈ on time ≈ on time
15:52≈ on time ≈ on time
16:02≈ on time ≈ on time
16:10≈ on time ≈ on time
16:21≈ on time ≈ on time
16:37on 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
Sat 7 NovMeppel 16:38Partial coverage0 min—
Fri 6 NovMeppel 16:49No data—
Thu 5 NovMeppel 16:390 min—
Wed 4 NovMeppel 16:390 min—
Tue 3 NovMeppel 16:430 min—
Mon 2 NovMeppel 16:490 min—
Sun 1 NovMeppel 16:36Partial coverage0 min—
Sat 31 OctMeppel 16:38Partial coverage0 min—
Fri 30 OctMeppel 16:380 min—
Thu 29 OctMeppel 16:360 min—
Wed 28 OctMeppel 16:390 min—
Tue 27 OctMeppel 16:39No data—
Mon 26 OctMeppel 16:43No data—
Sun 25 OctMeppel 16:38No data—
Sat 24 OctMeppel 16:38Partial coverage0 min—
Fri 23 OctMeppel 16:380 min—
Thu 22 OctMeppel 16:39No data—
Wed 21 OctMeppel 16:56No data—
Tue 20 OctMeppel 16:39No data—
Mon 19 OctMeppel 16:390 min—
Sun 18 OctMeppel 16:38Partial coverage0 min—
Sat 17 OctMeppel 16:38No data—
Fri 16 OctMeppel 16:57No data—
Thu 15 OctMeppel 16:38No data—
Wed 14 OctMeppel 16:390 min—
Tue 13 OctMeppel 16:38No data—
Mon 12 OctMeppel 16:390 min—
Sun 11 OctMeppel 16:41+1 min+2 min
Sat 10 OctGroningen 17:09Partial coverage+8 min+8 min
Fri 9 OctMeppel 16:380 min—