Train NS 6186 Groningen – Zwolle

Groningen 22:32 → Zwolle 23:37 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 22:32 from Groningen · Fri 6 Nov

Next departure 22:32 today · Groningen
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 14 full · 3 partial · 12 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 2 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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
22:32on time on time
22:35≈ on time ≈ on time
22:39≈ on time ≈ on time
22:52≈ on time ≈ +1 min
23:02≈ on time ≈ +1 min
23:10≈ on time ≈ +2 min
23:21≈ on time ≈ +2 min
23:37on time +2 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
Thu 5 Nov— 23:39No data—
Wed 4 Nov— 23:39+2 min+3 min
Tue 3 Nov— 23:39No data—
Mon 2 Nov— 23:39+6 min+6 min
Sun 1 NovMeppel 23:39Partial coverage0 min—
Sat 31 OctMeppel 23:38No data—
Fri 30 Oct— 23:38No data—
Thu 29 Oct— 23:200 min—
Wed 28 Oct— 23:38No data—
Tue 27 Oct— 23:380 min—
Mon 26 Oct— 23:38No data—
Sun 25 OctMeppel 23:38No data—
Sat 24 OctHaren 23:390 min—
Fri 23 Oct— 22:540 min—
Thu 22 Oct— 23:380 min—
Wed 21 Oct— 23:38No data—
Tue 20 Oct— 23:42No data—
Mon 19 Oct— 23:53No data—
Sun 18 OctMeppel 23:38Partial coverage0 min—
Sat 17 OctMeppel 23:410 min—
Fri 16 Oct— 23:41+2 min+2 min
Thu 15 Oct— 23:38No data—
Wed 14 Oct— 23:380 min—
Tue 13 Oct— 00:45No data—
Mon 12 Oct— 23:380 min—
Sun 11 OctMeppel 23:38Partial coverage0 min—
Sat 10 Oct— 23:39+1 min—
Fri 9 Oct— 23:380 min—
Thu 8 Oct— 23:380 min—
Wed 7 Oct— 23:380 min—