Train NS 6264 Groningen – Assen
It does not run today
Last recorded run: Thursday 5 November No data
Next service: Monday 16:52 from Groningen · Mon 9 Nov
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 +3 min · last fix heading to Haren +3 min
Distribution · 90 days
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 10
- 3–10 min 9% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=4
- 100% W n=2
- 100% T n=2
- — 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, 11 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 16:52 | on time | on time | |
| 16:55 | — | — | |
| 17:00 | — | — | |
| 17: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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | Haren 17:14 | No data | — |
| Wed 4 Nov | Haren 17:14 | No data | — |
| Tue 3 Nov | Haren 17:14Partial coverage | 0 min | — |
| Mon 2 Nov | Haren 17:14 | No data | — |
| Thu 29 Oct | Haren 17:14Partial coverage | 0 min | — |
| Wed 28 Oct | Haren 17:15Partial coverage | 0 min | — |
| Tue 27 Oct | Haren 17:35Partial coverage | 0 min | — |
| Mon 26 Oct | Haren 17:14Partial coverage | 0 min | — |
| Thu 22 Oct | Haren 17:25 | No data | — |
| Wed 21 Oct | Haren 17:14 | No data | — |
| Tue 20 Oct | Haren 17:14Partial coverage | 0 min | — |
| Mon 19 Oct | Haren 17:14 | No data | — |
| Thu 15 Oct | Haren 17:14 | No data | — |
| Wed 14 Oct | Haren 17:14 | No data | — |
| Tue 13 Oct | Haren 17:14 | No data | — |
| Mon 12 Oct | Haren 17:16Partial coverage | 0 min | — |
| Thu 8 Oct | Haren 17:23Partial coverage | +1 min | +1 min |
| Wed 7 Oct | Haren 17:14Partial coverage | 0 min | — |
| Tue 6 Oct | Haren 17:14Partial coverage | 0 min | — |
| Mon 5 Oct | Haren 17:15Partial coverage | +3 min | +3 min |
| Thu 1 Oct | Haren 17:14 | No data | — |
| Wed 30 Sept | Haren 17:14 | No data | — |
| Tue 29 Sept | Haren 17:14 | No data | — |
| Mon 28 Sept | Haren 17:14 | No data | — |
| Thu 24 Sept | Haren 17:14 | No data | — |
| Wed 23 Sept | Haren 17:14 | No data | — |
| Tue 22 Sept | Haren 17:14 | No data | — |
| Mon 21 Sept | Haren 17:14 | No data | — |
| Thu 17 Sept | Haren 17:14 | No data | — |
| Wed 16 Sept | Haren 17:15 | No data | — |