Train NS 6262 Groningen – Assen

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

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 16:22 from Groningen · Thu 12 Nov

Next departure 16:22 today · Groningen
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 10 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 38 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

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

  • Early 0% · 0
  • On time 100% · 12
  • 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=3
  • 100% 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, 12 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
16:22on time on time
16:25— —
16:30— —
16: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
Wed 11 NovHaren 16:44Partial coverage0 min—
Tue 10 NovHaren 16:44Partial coverage+1 min+1 min
Mon 9 NovHaren 16:44Partial coverage0 min—
Thu 5 NovHaren 16:44No data—
Wed 4 NovHaren 16:44No data—
Tue 3 NovHaren 16:44No data—
Mon 2 NovHaren 16:44No data—
Thu 29 OctHaren 16:44No data—
Wed 28 OctHaren 16:44Partial coverage0 min—
Tue 27 OctHaren 16:44Partial coverage0 min—
Mon 26 OctHaren 16:44Partial coverage0 min—
Thu 22 OctHaren 16:44No data—
Wed 21 OctHaren 16:44No data—
Tue 20 OctHaren 16:44Partial coverage0 min—
Mon 19 OctHaren 16:44No data—
Thu 15 OctHaren 16:44No data—
Wed 14 OctHaren 16:44No data—
Tue 13 OctHaren 16:44No data—
Mon 12 OctHaren 16:46Partial coverage0 min—
Thu 8 OctHaren 16:44Partial coverage0 min—
Wed 7 OctHaren 16:44Partial coverage0 min—
Tue 6 OctHaren 16:44Partial coverage0 min—
Mon 5 OctHaren 16:44Partial coverage0 min—
Thu 1 OctHaren 16:44No data—
Wed 30 SeptHaren 16:44No data—
Tue 29 SeptHaren 16:44No data—
Mon 28 SeptHaren 16:44No data—
Thu 24 SeptHaren 16:44No data—
Wed 23 SeptHaren 16:44No data—
Tue 22 SeptHaren 16:44No data—