Train NS 6179 Zwolle – Groningen

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

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 22:53 from Zwolle · Sun 8 Nov

Next departure 22:53 today · Zwolle
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 17 full · 4 partial · 8 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 22 full · 4 partial · 22 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 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

  • Mon 19 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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