Train NS 6127 Zwolle – Groningen

Zwolle 09:53 → Groningen 10:58 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Groningen Europapark at 11:09 0 min

  1. Zwolle09:53
  2. Meppel10:08
  3. Hoogeveen10:19
  4. Assen10:37
  5. Haren10:49
  6. Groningen Europapark10:55
  7. Groningen10:58

Next service: tomorrow 09:53 from Zwolle · Mon 9 Nov

Next departure 09:53 tomorrow · Zwolle
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 13 full · 8 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: 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

Worst days

  • Sun 11 Oct Max en route +3 min · last fix heading to Groningen Europapark +3 min

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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 100% F n=2
  • 100% S n=5
  • 75% S n=4

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
09:53on time on time
10:08≈ on time ≈ on time
10:19≈ on time ≈ +1 min
10:28≈ on time ≈ +1 min
10:37≈ on time ≈ +1 min
10:49≈ on time ≈ +1 min
10:55≈ on time ≈ +1 min
10:58on 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
Sun 8 NovGroningen Europapark 11:09Partial coverage0 min—
Sat 7 NovGroningen Europapark 11:09Partial coverage+1 min—
Fri 6 NovGroningen Europapark 11:09No data—
Thu 5 NovGroningen Europapark 11:09No data—
Wed 4 NovGroningen Europapark 11:090 min—
Tue 3 NovGroningen Europapark 11:09No data—
Mon 2 NovGroningen Europapark 11:13No data—
Sun 1 NovGroningen Europapark 11:10Partial coverage0 min—
Sat 31 OctGroningen Europapark 11:09Partial coverage0 min—
Fri 30 OctGroningen Europapark 11:09No data—
Thu 29 OctGroningen Europapark 11:090 min—
Wed 28 OctGroningen Europapark 11:090 min—
Tue 27 OctGroningen Europapark 11:09No data—
Mon 26 OctGroningen Europapark 11:090 min—
Sun 25 OctGroningen Europapark 11:09No data—
Sat 24 OctGroningen Europapark 11:09Partial coverage0 min—
Fri 23 OctGroningen Europapark 11:090 min—
Thu 22 OctGroningen Europapark 11:090 min—
Wed 21 OctGroningen Europapark 11:12No data—
Tue 20 OctGroningen Europapark 11:110 min—
Mon 19 OctGroningen Europapark 11:090 min—
Sun 18 OctGroningen Europapark 11:09Partial coverage0 min—
Sat 17 OctGroningen Europapark 11:10Partial coverage0 min—
Fri 16 OctGroningen Europapark 11:09No data—
Thu 15 OctGroningen Europapark 11:09No data—
Wed 14 OctGroningen Europapark 11:09No data—
Tue 13 OctGroningen Europapark 11:09No data—
Mon 12 OctGroningen Europapark 11:090 min—
Sun 11 OctGroningen Europapark 11:11+3 min+3 min
Sat 10 OctGroningen Europapark 11:09Partial coverage0 min—