Train NS 6182 Groningen – Zwolle

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:32 from Groningen · Sat 7 Nov

Next departure 21:32 today · Groningen
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 12 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 28 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: +3 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 11 Oct Max en route +17 min · last fix heading to Meppel +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
21:32on time on time
21:35≈ on time ≈ on time
21:39≈ on time ≈ on time
21:52≈ on time ≈ +1 min
22:02≈ on time ≈ +1 min
22:10≈ on time ≈ +2 min
22:21≈ on time ≈ +2 min
22: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
Fri 6 Nov— 22:380 min—
Thu 5 Nov— 22:39No data—
Wed 4 Nov— 22:43+3 min+3 min
Sun 1 NovMeppel 22:390 min—
Sat 31 OctMeppel 22:350 min—
Thu 29 Oct— 22:290 min—
Wed 28 Oct— 22:38No data—
Tue 27 Oct— 22:38No data—
Mon 26 Oct— 22:38No data—
Sun 25 OctMeppel 22:38No data—
Sat 24 OctMeppel 22:400 min—
Fri 23 Oct— 21:570 min—
Thu 22 Oct— 22:41No data—
Wed 21 Oct— 22:38No data—
Tue 20 Oct— 22:38No data—
Mon 19 Oct— 23:040 min—
Sun 18 OctMeppel 22:380 min—
Sat 17 OctMeppel 22:39No data—
Fri 16 Oct— 22:380 min—
Thu 15 Oct— 22:50No data—
Wed 14 Oct— 22:38No data—
Tue 13 Oct— 22:39No data—
Mon 12 Oct— 22:380 min—
Sun 11 OctMeppel 23:01+17 min+17 min
Sat 10 OctBeilen 22:43+2 min+2 min
Fri 9 Oct— 22:380 min—
Thu 8 Oct— 22:390 min—
Wed 7 Oct— 22:370 min—
Tue 6 Oct— 22:43+2 min+2 min
Mon 5 Oct— 22:380 min—