Train NS 6134 Groningen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Meppel at 10:38 No data

  1. Groningen09:32
  2. Groningen Europapark09:35
  3. Haren09:39
  4. Beilen10:02
  5. Hoogeveen10:10
  6. Meppel10:21
  7. Zwolle10:37

Next service: tomorrow 09:32 from Groningen · Sat 7 Nov

Next departure 09:32 tomorrow · Groningen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 6 full · 12 partial · 12 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 7 full · 13 partial · 69 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 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

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