Train NS 6228 Groningen – Assen

Groningen 07:52 → Assen 08:12 Mon, Tue, Wed, Thu 0 h 20 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 07:52 from Groningen · Tue 17 Nov

Next departure 07:52 today · Groningen
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 4 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 34 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 Assen, 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=4
  • 100% W n=4
  • 100% T n=3
  • — 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, 15 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
07:52on time on time
07:55— —
08:00— —
08:12— —

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