Train NS 6138 Groningen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Meppel at 11:47 No data

  1. Groningen10:32
  2. Groningen Europapark10:35
  3. Haren10:39
  4. Beilen11:02
  5. Hoogeveen11:10
  6. Meppel11:21
  7. Zwolle11:37

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

Next departure 10:32 tomorrow · Groningen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 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

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