Train NS 6118 Groningen – Zwolle

Groningen 05:32 → Zwolle 06:37 Mon, Tue, Wed, Thu, Fri 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 05:32 from Groningen · Mon 9 Nov

Next departure 05:32 Monday · Groningen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 8 full · 11 partial · 2 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 10 full · 12 partial · 42 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 80% W n=5
  • 80% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
05:32on time on time
05:35≈ on time ≈ on time
05:39≈ on time ≈ on time
05:52≈ on time ≈ on time
06:02≈ on time ≈ +1 min
06:10≈ on time ≈ +1 min
06:21≈ on time ≈ +1 min
06:37on 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
Fri 6 NovMeppel 06:38No data—
Thu 5 NovMeppel 06:39Partial coverage0 min—
Wed 4 NovMeppel 06:39+1 min+1 min
Tue 3 NovMeppel 06:380 min—
Mon 2 NovMeppel 07:02No data—
Fri 30 OctMeppel 06:38Partial coverage0 min—
Thu 29 OctMeppel 06:38Partial coverage0 min—
Wed 28 OctMeppel 06:45+3 min+3 min
Tue 27 OctMeppel 06:390 min—
Mon 26 OctMeppel 06:38Partial coverage0 min—
Fri 23 OctMeppel 06:38Partial coverage0 min—
Thu 22 OctMeppel 06:38Partial coverage0 min—
Wed 21 OctMeppel 06:380 min—
Tue 20 OctMeppel 06:380 min—
Mon 19 OctMeppel 06:38Partial coverage0 min—
Fri 16 OctMeppel 06:40Partial coverage+1 min+1 min
Thu 15 OctMeppel 06:38Partial coverage0 min—
Wed 14 OctMeppel 06:39+1 min—
Tue 13 OctMeppel 06:380 min—
Mon 12 OctMeppel 06:38Partial coverage0 min—
Fri 9 OctMeppel 06:38Partial coverage0 min—
Thu 8 OctMeppel 06:51Partial coverage+7 min+8 min
Wed 7 OctGroningen 06:40+1 min+1 min
Tue 6 OctMeppel 06:390 min—
Mon 5 OctMeppel 06:37No data—
Fri 2 OctMeppel 06:36No data—
Thu 1 OctMeppel 06:36No data—
Wed 30 SeptMeppel 06:37No data—
Tue 29 SeptMeppel 06:36No data—
Mon 28 SeptMeppel 06:36No data—