Train NS 6187 Zwolle – Groningen

Zwolle 00:53 → Groningen 01:58 Mon, Tue, Wed, Thu, Fri, Sat 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:59 0 min

  1. Zwolle00:53
  2. Meppel01:08
  3. Hoogeveen01:20
  4. Assen01:37
  5. Haren01:50
  6. Groningen Europapark01:54
  7. Groningen01:58

Next service: Monday 00:53 from Zwolle · Mon 9 Nov

Next departure 00:53 Monday · Zwolle
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 22 full · 1 partial · 1 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 25 full · 1 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Groningen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 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, 26 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
00:53on time on time
01:08≈ on time ≈ on time
01:20≈ on time ≈ on time
01:28≈ on time ≈ on time
01:37≈ on time ≈ on time
01:50≈ on time ≈ on time
01:54≈ on time ≈ on time
01:58on time on time

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 Nov— 01:590 min—
Fri 6 Nov— 02:020 min—
Thu 5 Nov— 02:180 min—
Wed 4 Nov— 01:590 min—
Tue 3 Nov— 01:590 min—
Sat 31 Oct— 00:590 min—
Fri 30 Oct— 02:080 min—
Wed 28 Oct— 01:59No data—
Tue 27 Oct— 01:590 min—
Sun 25 Oct— 02:260 min—
Sat 24 Oct— 02:140 min—
Fri 23 Oct— 02:100 min—
Thu 22 Oct— 02:040 min—
Wed 21 Oct— 02:040 min—
Tue 20 Oct— 02:040 min—
Sun 18 OctBeilen 01:59Partial coverage0 min—
Sat 17 Oct— 00:590 min—
Fri 16 Oct— 02:030 min—
Thu 15 Oct— 01:590 min—
Wed 14 Oct— 01:590 min—
Tue 13 Oct— 01:590 min—
Sun 11 Oct— 02:00+3 min+3 min
Sat 10 Oct— 01:590 min—
Fri 9 Oct— 02:000 min—
Thu 8 Oct— 01:590 min—
Wed 7 Oct— 01:590 min—
Tue 6 Oct— 01:590 min—