Train NS 6146 Groningen – Zwolle

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 12:32 from Groningen · Sun 8 Nov

Next departure 12:32 today · Groningen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 11 full · 7 partial · 11 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 16 full · 7 partial · 65 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

Worst days

  • Fri 9 Oct Max en route +12 min · last fix heading to Meppel +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=3
  • 100% T n=4
  • 50% F n=2
  • 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, 23 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
12:32on time on time
12:35≈ on time ≈ on time
12:39≈ on time ≈ on time
12:52≈ on time ≈ on time
13:02≈ on time ≈ on time
13:10≈ on time ≈ on time
13:21≈ on time ≈ on time
13: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
Sat 7 NovMeppel 13:38Partial coverage0 min—
Fri 6 NovMeppel 13:38No data—
Thu 5 NovMeppel 13:380 min—
Wed 4 NovMeppel 13:390 min—
Tue 3 NovMeppel 13:380 min—
Mon 2 NovMeppel 13:390 min—
Sun 1 NovMeppel 13:39Partial coverage0 min—
Sat 31 OctMeppel 13:38Partial coverage0 min—
Fri 30 OctMeppel 13:38Partial coverage0 min—
Thu 29 OctMeppel 13:380 min—
Wed 28 OctMeppel 13:410 min—
Tue 27 OctMeppel 13:390 min—
Mon 26 OctMeppel 13:38No data—
Sun 25 OctMeppel 13:38No data—
Sat 24 OctMeppel 13:38Partial coverage0 min—
Fri 23 OctMeppel 13:43No data—
Thu 22 OctMeppel 13:390 min—
Wed 21 OctMeppel 13:38No data—
Tue 20 OctMeppel 13:390 min—
Mon 19 OctMeppel 13:380 min—
Sun 18 OctMeppel 13:36Partial coverage0 min—
Sat 17 OctMeppel 13:38No data—
Fri 16 OctMeppel 13:38No data—
Thu 15 OctMeppel 13:41No data—
Wed 14 OctMeppel 13:38No data—
Tue 13 OctMeppel 13:38No data—
Mon 12 OctMeppel 13:39No data—
Sun 11 OctMeppel 13:380 min—
Sat 10 OctMeppel 13:38Partial coverage+2 min+2 min
Fri 9 OctMeppel 13:51+12 min+12 min