Train NS 6268 Groningen – Assen

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

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Monday 17:52 from Groningen · Mon 9 Nov

Next departure 17:52 Monday · Groningen
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 1 full · 5 partial · 11 no data
On-time · 90 days
78%
7/9 runs under 3 min
RT coverage: 1 full · 8 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Mon 5 Oct Max en route +8 min · last fix heading to Haren +8 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Haren +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 7
  • 3–10 min 22% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=2
  • 0% T n=1
  • — 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, 9 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
17:52on time on time
17:55— —
18:00— —
18: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
Thu 5 NovHaren 18:13No data—
Wed 4 NovHaren 18:14No data—
Tue 3 NovHaren 18:14No data—
Mon 2 NovHaren 18:14No data—
Thu 29 OctHaren 18:14No data—
Wed 28 OctHaren 18:13Partial coverage0 min—
Tue 27 OctHaren 18:14Partial coverage0 min—
Mon 26 OctHaren 18:15Partial coverage0 min—
Thu 22 OctHaren 18:13No data—
Wed 21 OctHaren 18:14No data—
Tue 20 OctHaren 18:140 min—
Mon 19 OctHaren 18:14No data—
Thu 15 OctHaren 18:14No data—
Wed 14 OctHaren 18:15No data—
Tue 13 OctHaren 18:14No data—
Mon 12 OctHaren 18:14Partial coverage0 min—
Thu 8 OctHaren 18:16Partial coverage+3 min+3 min
Wed 7 OctHaren 18:14Partial coverage0 min—
Tue 6 OctHaren 18:14Partial coverage0 min—
Mon 5 OctHaren 18:28Partial coverage+8 min+8 min
Thu 1 OctHaren 18:15No data—
Wed 30 SeptHaren 18:14No data—
Tue 29 SeptHaren 18:14No data—
Mon 28 SeptHaren 18:14No data—
Thu 24 SeptGroningen Europapark 18:10No data—
Wed 23 SeptHaren 18:14No data—
Tue 22 SeptHaren 18:14No data—
Mon 21 SeptHaren 18:14No data—
Thu 17 SeptHaren 18:14No data—
Wed 16 SeptHaren 18:14No data—