Train NS 6222 Groningen – Assen

Groningen 06:22 → Assen 06:42 Mon, Tue, Wed, Thu 0 h 20 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Haren at 06:49 +5 min

  1. Groningen06:22
  2. Groningen Europapark06:25
  3. Haren06:30
  4. Assen06:42

Next service: tomorrow 06:22 from Groningen · Wed 18 Nov

Next departure 06:22 tomorrow · Groningen
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 1 full · 14 partial · 3 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 1 full · 20 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Assen, 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 17 Nov Max en route +5 min · last fix heading to Haren +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 83% T n=6
  • 100% W n=5
  • 100% T n=5
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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
06:22on time on time
06:25— —
06:30— —
06:42— —

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
Tue 17 NovHaren 06:49Partial coverage+5 min+5 min
Mon 16 NovHaren 06:44Partial coverage0 min—
Thu 12 NovHaren 06:44Partial coverage+1 min+1 min
Wed 11 NovHaren 06:44Partial coverage0 min—
Tue 10 NovHaren 06:44+1 min+1 min
Mon 9 NovHaren 06:49Partial coverage+3 min+3 min
Thu 5 NovHaren 06:44No data—
Wed 4 NovHaren 06:44Partial coverage0 min—
Tue 3 NovHaren 06:44No data—
Mon 2 NovHaren 06:44No data—
Thu 29 OctHaren 06:44Partial coverage0 min—
Wed 28 OctHaren 06:44Partial coverage+2 min+2 min
Tue 27 OctHaren 06:44Partial coverage0 min—
Mon 26 OctHaren 06:44Partial coverage0 min—
Thu 22 OctHaren 06:44Partial coverage0 min—
Wed 21 OctHaren 06:45Partial coverage+1 min+1 min
Tue 20 OctHaren 06:44Partial coverage0 min—
Mon 19 OctHaren 06:44Partial coverage0 min—
Thu 15 OctHaren 06:44Partial coverage0 min—
Wed 14 OctHaren 06:45Partial coverage+2 min+2 min
Tue 13 OctHaren 06:44Partial coverage+1 min+1 min
Mon 12 OctHaren 06:45Partial coverage0 min—
Thu 8 OctHaren 06:44Partial coverage0 min—
Wed 7 OctHaren 06:44No data—
Tue 6 OctHaren 06:44Partial coverage0 min—
Mon 5 OctHaren 06:54No data—
Thu 1 OctHaren 06:44No data—
Wed 30 SeptHaren 06:44No data—
Tue 29 SeptHaren 06:44No data—
Mon 28 SeptHaren 06:44No data—