Train NS 6172 Groningen – Zwolle

Groningen 19:02 → Zwolle 20:07 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 20:08 0 min

  1. Groningen19:02
  2. Groningen Europapark19:05
  3. Haren19:09
  4. Beilen19:32
  5. Hoogeveen19:40
  6. Meppel19:51
  7. Zwolle20:07

Next service: tomorrow 19:02 from Groningen · Sat 7 Nov

Next departure 19:02 tomorrow · Groningen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 10 full · 8 partial · 10 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 13 full · 8 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 31 Oct Max en route +6 min · last fix heading to Meppel +6 min
  • Thu 8 Oct Max en route +5 min · last fix heading to — +5 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 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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