Train NS 6130 Groningen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Meppel at 09:39 No data

  1. Groningen08:32
  2. Groningen Europapark08:35
  3. Haren08:39
  4. Beilen09:02
  5. Hoogeveen09:10
  6. Meppel09:21
  7. Zwolle09:37

Next service: tomorrow 08:32 from Groningen · Fri 6 Nov

Next departure 08:32 tomorrow · Groningen
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 10 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 9 full · 12 partial · 68 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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