Train NS 6171 Zwolle – Groningen

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

Running now · updated 21:50

Heading to Groningen 0 min

Estimated arrival at Groningen 21:58 · 23 km/h

  1. Zwolle20:53
  2. Meppel21:08
  3. Hoogeveen21:19
  4. Assen21:37
  5. Haren21:49
  6. Groningen Europapark21:55
  7. Groningen21:58

Today it is running no worse than usual: typical arrival delay is 0 min; 88% of the last 17 runs arrived on time.

On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 10 full · 7 partial · 12 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 15 full · 7 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 6 Nov Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 22 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 10Today
20:53on time on time
21:08≈ on time ≈ +1 min
21:19≈ on time ≈ +2 min
21:28≈ on time ≈ +2 min
21:37≈ on time ≈ +3 min
21:49≈ on time ≈ +3 min
21:55≈ on time ≈ +4 min
21:58on time +4 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 21:49Partial coverage0 min—
Sat 7 NovGroningen Europapark 22:09Partial coverage0 min—
Fri 6 Nov— 22:02+4 min+5 min
Thu 5 Nov— 21:59No data—
Wed 4 Nov— 21:590 min—
Tue 3 Nov— 21:59No data—
Mon 2 Nov— 21:590 min—
Sun 1 NovGroningen Europapark 22:09Partial coverage0 min—
Sat 31 OctGroningen Europapark 22:09No data—
Fri 30 Oct— 21:59No data—
Thu 29 Oct— 21:58+4 min+4 min
Wed 28 Oct— 22:180 min—
Tue 27 Oct— 22:000 min—
Mon 26 Oct— 22:07No data—
Sun 25 OctGroningen Europapark 22:09No data—
Sat 24 OctGroningen Europapark 22:09Partial coverage0 min—
Fri 23 Oct— 21:590 min+2 min
Thu 22 Oct— 22:00No data—
Wed 21 Oct— 22:00No data—
Tue 20 Oct— 21:59No data—
Mon 19 Oct— 21:590 min—
Sun 18 OctGroningen Europapark 22:09Partial coverage0 min—
Sat 17 OctGroningen Europapark 22:09No data—
Fri 16 Oct— 21:59+1 min—
Thu 15 Oct— 22:00No data—
Tue 13 Oct— 22:00No data—
Mon 12 Oct— 22:000 min—
Sun 11 OctGroningen Europapark 22:09Partial coverage0 min—
Sat 10 OctGroningen Europapark 22:09Partial coverage0 min—
Fri 9 Oct— 22:00+3 min+4 min