Train NS 6192 Groningen – Assen

Groningen 00:02 → Assen 00:22 Daily 0 h 20 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:23 0 min

  1. Groningen00:02
  2. Groningen Europapark00:05
  3. Haren00:09
  4. Assen00:22

Next service: tomorrow 00:02 from Groningen · Mon 16 Nov

Next departure 00:02 tomorrow · Groningen
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 2 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 30 full · 2 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 11 Oct Max en route +4 min · last fix heading to Haren +4 min
  • Sat 24 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
00:02on time on time
00:05≈ on time ≈ on time
00:09≈ on time ≈ on time
00:22on time +1 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
Sun 15 Nov— 00:230 min—
Sat 14 Nov— 00:23+1 min—
Fri 13 Nov— 00:230 min—
Thu 12 Nov— 00:230 min—
Wed 11 Nov— 00:230 min—
Tue 10 Nov— 00:230 min—
Sun 8 NovHaren 00:240 min—
Sat 7 Nov— 00:230 min—
Fri 6 Nov— 00:23No data—
Thu 5 Nov— 00:240 min—
Wed 4 Nov— 00:440 min—
Sun 1 NovHaren 00:24Partial coverage0 min—
Sat 31 Oct— 00:230 min—
Fri 30 Oct— 00:230 min—
Thu 29 Oct— 00:220 min—
Wed 28 Oct— 00:230 min—
Tue 27 Oct— 00:230 min—
Sun 25 OctHaren 00:23No data—
Sat 24 Oct— 00:28+3 min+3 min
Fri 23 Oct— 00:230 min—
Thu 22 Oct— 00:230 min—
Wed 21 Oct— 00:220 min—
Tue 20 Oct— 00:28+2 min+2 min
Sun 18 OctHaren 00:230 min—
Sat 17 OctHaren 00:230 min—
Fri 16 Oct— 00:24No data—
Thu 15 Oct— 00:230 min—
Wed 14 Oct— 00:230 min—
Tue 13 Oct— 00:230 min—
Sun 11 OctHaren 00:31+4 min+4 min