Train NS 6163 Zwolle – Groningen

Zwolle 18:53 → Groningen 19:58 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Meppel at 19:59 0 min

  1. Zwolle18:53
  2. Meppel19:08
  3. Hoogeveen19:19
  4. Assen19:37
  5. Haren19:49
  6. Groningen Europapark19:55
  7. Groningen19:58

Next service: tomorrow 18:53 from Zwolle · Sat 21 Nov

Next departure 18:53 tomorrow · Zwolle
On-time · 30 days
83%
20/24 runs under 3 min
RT coverage: 20 full · 4 partial · 6 no data
On-time · 90 days
89%
32/36 runs under 3 min
RT coverage: 32 full · 4 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

Worst days

  • Thu 19 Nov Max en route +18 min · last fix heading to — +17 min
  • Fri 23 Oct Max en route +14 min · last fix heading to Beilen +14 min
  • Mon 16 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Zwolle +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 32
  • 3–10 min 6% · 2
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=4
  • 100% W n=4
  • 83% T n=6
  • 60% F n=5
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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
18:53on time on time
19:08≈ on time ≈ +1 min
19:19≈ on time ≈ +1 min
19:28≈ on time ≈ +2 min
19:37≈ on time ≈ +2 min
19:49≈ on time ≈ +3 min
19:55≈ on time ≈ +3 min
19:58on time +3 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 20 NovMeppel 19:59Partial coverage0 min—
Thu 19 Nov— 20:34+17 min+18 min
Wed 18 Nov— 19:59+1 min—
Tue 17 Nov— 20:04+3 min+4 min
Mon 16 Nov— 20:09+4 min+4 min
Sun 15 NovGroningen Europapark 20:12+3 min+4 min
Sat 14 NovGroningen Europapark 20:090 min—
Fri 13 NovZwolle 20:08Partial coverage+4 min+4 min
Thu 12 Nov— 20:08+3 min+4 min
Wed 11 Nov— 19:590 min—
Tue 10 Nov— 19:59+1 min—
Mon 9 Nov— 19:590 min—
Sun 8 NovGroningen Europapark 20:090 min—
Sat 7 NovGroningen Europapark 20:090 min—
Fri 6 Nov— 19:590 min—
Thu 5 Nov— 19:590 min—
Wed 4 Nov— 19:590 min—
Tue 3 Nov— 20:02No data—
Mon 2 Nov— 20:02No data—
Sun 1 NovGroningen Europapark 20:090 min—
Sat 31 OctGroningen Europapark 20:090 min—
Fri 30 OctZwolle 19:59No data—
Thu 29 Oct— 19:590 min—
Wed 28 Oct— 20:00No data—
Tue 27 Oct— 20:05No data—
Mon 26 OctAssen 20:23Partial coverage0 min—
Sun 25 OctGroningen Europapark 20:09No data—
Sat 24 OctGroningen Europapark 20:120 min—
Fri 23 OctBeilen 20:27Partial coverage+14 min+14 min
Thu 22 Oct— 20:000 min—