Train NS 6122 Groningen – Zwolle

Groningen 06:32 → Zwolle 07:37 Mon, Tue, Wed, Thu, Fri, Sat 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 06:32 from Groningen · Mon 9 Nov

Next departure 06:32 today · Groningen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 18 full · 4 partial · 2 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 22 full · 5 partial · 48 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

  • Wed 7 Oct Max en route +4 min · last fix heading to Groningen +4 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 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 80% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=5
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
06:32on time on time
06:35≈ on time ≈ on time
06:39≈ on time ≈ on time
06:52≈ on time ≈ +1 min
07:02≈ on time ≈ +1 min
07:10≈ on time ≈ +1 min
07:21≈ on time ≈ +1 min
07: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
Sat 7 NovMeppel 07:39Partial coverage0 min—
Fri 6 NovMeppel 07:39No data—
Thu 5 NovMeppel 07:390 min—
Wed 4 NovMeppel 07:390 min—
Tue 3 NovMeppel 07:380 min—
Mon 2 NovMeppel 07:39No data—
Sat 31 OctMeppel 07:38Partial coverage+1 min+1 min
Fri 30 OctMeppel 07:380 min—
Thu 29 OctMeppel 07:360 min—
Wed 28 OctMeppel 07:390 min—
Tue 27 OctMeppel 07:390 min—
Mon 26 OctMeppel 07:42+2 min+2 min
Sat 24 OctMeppel 07:37Partial coverage0 min—
Fri 23 OctMeppel 07:38+2 min+2 min
Thu 22 OctMeppel 07:380 min—
Wed 21 OctMeppel 07:360 min—
Tue 20 OctMeppel 07:45+1 min—
Mon 19 OctMeppel 07:360 min—
Sat 17 OctMeppel 07:38Partial coverage0 min—
Fri 16 OctMeppel 07:380 min—
Thu 15 OctMeppel 07:380 min—
Wed 14 OctAssen 07:380 min—
Tue 13 OctMeppel 07:390 min—
Mon 12 OctMeppel 07:380 min—
Sat 10 OctMeppel 07:38Partial coverage0 min—
Fri 9 OctMeppel 07:380 min—
Thu 8 OctMeppel 07:39+1 min+1 min
Wed 7 OctGroningen 07:45+4 min+4 min
Tue 6 OctMeppel 07:390 min—
Mon 5 OctMeppel 07:37No data—