Train NS 6164 Groningen – Zwolle

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 17:02 from Groningen · Sun 8 Nov

Next departure 17:02 today · Groningen
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 14 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 1 full · 19 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 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

  • Wed 7 Oct Max en route +8 min · last fix heading to Meppel +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 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=3
  • 67% W n=3
  • 100% T n=1
  • 100% F n=2
  • 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, 20 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
17:02on time on time
17:05— —
17:09— —
17:22— —
17:32— —
17:40— —
17:51— —
18:07— —

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 NovMeppel 18:08Partial coverage0 min—
Fri 6 NovMeppel 18:08Partial coverage0 min—
Thu 5 NovMeppel 18:09No data—
Wed 4 NovMeppel 18:09Partial coverage0 min—
Tue 3 NovMeppel 18:09No data—
Mon 2 NovMeppel 18:09No data—
Sun 1 NovMeppel 18:09Partial coverage0 min—
Sat 31 OctMeppel 18:06Partial coverage0 min—
Fri 30 OctMeppel 18:08No data—
Thu 29 OctMeppel 18:11No data—
Wed 28 OctMeppel 18:08Partial coverage0 min—
Tue 27 OctMeppel 18:25Partial coverage0 min—
Mon 26 OctMeppel 18:08Partial coverage0 min—
Sun 25 OctMeppel 18:08No data—
Sat 24 OctMeppel 18:08Partial coverage0 min—
Fri 23 OctMeppel 18:10No data—
Thu 22 OctMeppel 18:08No data—
Wed 21 OctMeppel 18:09No data—
Tue 20 OctMeppel 18:11Partial coverage0 min—
Mon 19 OctMeppel 18:05No data—
Sun 18 OctMeppel 18:07Partial coverage0 min—
Sat 17 OctMeppel 18:08Partial coverage0 min—
Fri 16 OctMeppel 18:08No data—
Thu 15 OctMeppel 18:15No data—
Wed 14 OctMeppel 18:08No data—
Tue 13 OctMeppel 18:09No data—
Mon 12 OctMeppel 18:09Partial coverage0 min—
Sun 11 OctMeppel 18:08Partial coverage0 min—
Sat 10 OctMeppel 18:08Partial coverage+1 min—
Fri 9 OctMeppel 18:08Partial coverage0 min—