Train NS 6156 Groningen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Meppel at 16:08 0 min

  1. Groningen15:02
  2. Groningen Europapark15:05
  3. Haren15:09
  4. Beilen15:32
  5. Hoogeveen15:40
  6. Meppel15:51
  7. Zwolle16:07

Next service: tomorrow 15:02 from Groningen · Mon 9 Nov

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

  • Fri 9 Oct Max en route +8 min · last fix heading to Haren +8 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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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