Train NS 6174 Groningen – Zwolle

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

It has not run yet today

Last recorded run: Friday 6 November +7 min

Next service: today 19:32 from Groningen · Sat 7 Nov

Next departure 19:32 today · Groningen
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 12 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 14 full · 7 partial · 35 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: +2 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

  • Tue 6 Oct Max en route +8 min · last fix heading to — +8 min
  • Fri 6 Nov Max en route +8 min · last fix heading to — +7 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=3
  • 50% T n=2
  • 100% W n=2
  • 100% T n=2
  • 80% F n=5
  • 100% 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:32on time on time
19:35≈ on time ≈ on time
19:39≈ on time ≈ +1 min
19:52≈ on time ≈ +2 min
20:02≈ on time ≈ +3 min
20:10≈ on time ≈ +3 min
20:21≈ on time ≈ +4 min
20:37+1 min +6 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:53+7 min+8 min
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:39+2 min+2 min
Tue 3 Nov— 20:39No data—
Mon 2 Nov— 20:44No data—
Sun 1 NovMeppel 20:34Partial coverage0 min—
Sat 31 OctMeppel 20:36Partial coverage0 min—
Fri 30 Oct— 20:380 min—
Thu 29 Oct— 20:38+2 min+2 min
Wed 28 Oct— 20:38No data—
Tue 27 Oct— 20:510 min—
Mon 26 OctAssen 20:41No data—
Sun 25 OctMeppel 20:38No data—
Sat 24 OctMeppel 20:40Partial coverage0 min—
Fri 23 Oct— 20:38+2 min+2 min
Thu 22 Oct— 20:39No data—
Wed 21 Oct— 20:38No data—
Tue 20 Oct— 20:38No data—
Mon 19 Oct— 20:300 min—
Sun 18 OctMeppel 20:39Partial coverage+1 min+2 min
Sat 17 OctMeppel 20:37Partial coverage0 min—
Fri 16 OctAssen 20:380 min—
Thu 15 Oct— 20:40No data—
Wed 14 OctHaren 20:38No data—
Tue 13 Oct— 20:39No data—
Mon 12 Oct— 20:490 min—
Sun 11 OctMeppel 20:38Partial coverage0 min—
Sat 10 OctMeppel 20:39Partial coverage0 min—
Fri 9 Oct— 20:38+1 min+1 min
Thu 8 Oct— 20:50+2 min+2 min