Train NS 6125 Zwolle – Groningen

Zwolle 09:23 → Groningen 10:28 Mon, Tue, Wed, Thu, Fri, Sat 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Groningen Europapark at 10:39 0 min

  1. Zwolle09:23
  2. Meppel09:38
  3. Hoogeveen09:49
  4. Assen10:07
  5. Haren10:19
  6. Groningen Europapark10:25
  7. Groningen10:28

Next service: Monday 09:23 from Zwolle · Mon 9 Nov

Next departure 09:23 Monday · Zwolle
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 11 full · 5 partial · 10 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 14 full · 5 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Groningen, 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 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, 19 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
09:23on time on time
09:38≈ on time ≈ on time
09:49≈ on time ≈ on time
09:58≈ on time ≈ on time
10:07≈ on time ≈ on time
10:19≈ on time ≈ on time
10:25≈ on time ≈ on time
10:28on time on time

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 NovGroningen Europapark 10:39Partial coverage0 min—
Fri 6 NovGroningen Europapark 10:39No data—
Thu 5 NovGroningen Europapark 10:39No data—
Wed 4 NovGroningen Europapark 10:390 min—
Tue 3 NovGroningen Europapark 10:400 min—
Mon 2 NovGroningen Europapark 10:390 min—
Sat 31 OctGroningen Europapark 10:39Partial coverage0 min—
Fri 30 OctGroningen Europapark 10:390 min—
Thu 29 OctGroningen Europapark 10:390 min—
Wed 28 OctGroningen Europapark 10:390 min—
Tue 27 OctGroningen Europapark 10:410 min—
Mon 26 OctGroningen Europapark 10:39No data—
Sat 24 OctGroningen Europapark 10:39Partial coverage0 min—
Fri 23 OctGroningen Europapark 10:390 min—
Thu 22 OctGroningen Europapark 10:41No data—
Wed 21 OctGroningen Europapark 10:39No data—
Tue 20 OctGroningen Europapark 10:390 min—
Mon 19 OctGroningen Europapark 10:390 min—
Sat 17 OctGroningen Europapark 10:39Partial coverage0 min—
Fri 16 OctGroningen Europapark 10:39No data—
Thu 15 OctZwolle 10:58No data—
Wed 14 OctGroningen Europapark 10:39No data—
Tue 13 OctGroningen Europapark 10:39No data—
Mon 12 OctGroningen Europapark 10:39No data—
Sat 10 OctGroningen Europapark 10:39Partial coverage0 min—
Fri 9 OctGroningen Europapark 10:390 min—
Thu 8 OctGroningen Europapark 10:390 min—
Wed 7 OctGroningen Europapark 12:020 min—
Tue 6 OctGroningen Europapark 10:390 min—
Mon 5 OctGroningen Europapark 10:39No data—