Train NS 6190 Groningen – Zwolle

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

Running now · updated 23:45

Heading to Zwolle 0 min

Estimated arrival at Zwolle 00:37 · 128 km/h

  1. Groningen23:32
  2. Groningen Europapark23:35
  3. Haren23:39
  4. Beilen00:02
  5. Hoogeveen00:10
  6. Meppel00:21
  7. Zwolle00:37

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 27 runs arrived on time.

On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 24 full · 3 partial · 0 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 26 full · 3 partial · 13 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 Zwolle, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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 10Today
23:32on time on time
23:35≈ on time ≈ on time
23:39≈ on time ≈ on time
23:52≈ on time ≈ on time
00:02≈ on time ≈ on time
00:10≈ on time ≈ on time
00:21≈ on time ≈ on time
00:37on 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
Thu 5 Nov— 23:440 min—
Wed 4 Nov— 00:390 min—
Tue 3 Nov— 00:390 min—
Mon 2 Nov— 00:380 min—
Sun 1 NovMeppel 00:38Partial coverage0 min—
Thu 29 Oct— 00:380 min—
Wed 28 Oct— 00:380 min—
Tue 27 Oct— 00:390 min—
Mon 26 Oct— 00:380 min—
Sun 25 OctMeppel 00:38Partial coverage0 min—
Sat 24 Oct— 00:410 min—
Fri 23 Oct— 00:390 min—
Thu 22 Oct— 00:380 min—
Wed 21 Oct— 00:380 min—
Tue 20 Oct— 00:380 min—
Sun 18 OctMeppel 00:380 min—
Sat 17 OctMeppel 00:350 min—
Fri 16 Oct— 00:340 min+6 min
Thu 15 Oct— 00:380 min—
Wed 14 Oct— 00:380 min—
Tue 13 Oct— 00:390 min—
Mon 12 Oct— 00:380 min—
Sun 11 OctMeppel 00:38Partial coverage0 min—
Sat 10 Oct— 00:390 min—
Fri 9 Oct— 00:410 min+4 min
Thu 8 Oct— 00:380 min—
Wed 7 Oct— 00:380 min—
Tue 6 Oct— 00:380 min—
Mon 5 OctHoogeveen 00:380 min—
Sun 4 OctMeppel 00:35No data—