Train NS 6120 Groningen – Zwolle

Groningen 06:02 → Zwolle 07:07 Mon, Tue, Wed, Thu, Fri, Sat 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 7 November +3 min

Next service: tomorrow 06:02 from Groningen · Mon 9 Nov

Next departure 06:02 tomorrow · Groningen
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 20 full · 3 partial · 2 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 24 full · 3 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 9 Oct Max en route +9 min · last fix heading to Meppel +9 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Meppel +5 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Meppel +5 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Meppel +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 85% · 23
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 80% T n=5
  • 100% W n=5
  • 75% T n=4
  • 75% 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:02on time on time
06:05≈ on time ≈ on time
06:09≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:32≈ on time ≈ +2 min
06:40≈ on time ≈ +3 min
06:51≈ on time ≈ +4 min
07:07on time +5 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:13Partial coverage+3 min+3 min
Fri 6 NovMeppel 07:13No data—
Thu 5 NovMeppel 07:09No data—
Wed 4 NovMeppel 07:090 min—
Tue 3 NovMeppel 07:080 min—
Mon 2 NovMeppel 07:090 min—
Sat 31 OctMeppel 07:06Partial coverage0 min—
Fri 30 OctMeppel 07:08+1 min—
Thu 29 OctMeppel 07:080 min—
Wed 28 OctMeppel 07:13+2 min+2 min
Tue 27 OctMeppel 07:090 min—
Mon 26 OctMeppel 07:15+4 min+4 min
Sat 24 OctMeppel 07:080 min—
Fri 23 OctMeppel 07:080 min—
Thu 22 OctMeppel 07:09+1 min+1 min
Wed 21 OctMeppel 07:08+1 min+1 min
Tue 20 OctMeppel 07:19+5 min+5 min
Mon 19 OctMeppel 07:08+1 min—
Sat 17 OctMeppel 07:09Partial coverage0 min—
Fri 16 OctMeppel 07:080 min—
Thu 15 OctMeppel 07:18+5 min+5 min
Wed 14 OctMeppel 07:080 min—
Tue 13 OctMeppel 07:080 min—
Mon 12 OctMeppel 07:080 min—
Sat 10 OctMeppel 07:080 min—
Fri 9 OctMeppel 07:25+9 min+9 min
Thu 8 OctMeppel 07:060 min—
Wed 7 OctHaren 07:080 min—
Tue 6 OctMeppel 07:090 min—
Mon 5 OctMeppel 07:09No data—