Train Blauwnet A 31066 Mariënberg → Almelo
Blauwnet A 31066 Mariënberg–Almelo: final delay under 3 min on 16 of its 19 runs with data in the last 30 days (84%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 18:05 (GMT+1).
An alert on this phone or computer when the 31066 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Vriezenveen at 17:52 0 min
- Mariënberg17:25
- Vroomshoop17:30
- Daarlerveen17:33
- Vriezenveen17:38
- Almelo17:43
Next service: tomorrow 17:25 from Mariënberg · Sun 22 Nov
Last 30 days
Arrival delay at Almelo, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 17 Nov Max en route +6 min · last fix heading to Vriezenveen +6 min
- Tue 6 Oct Max en route +5 min · last fix heading to Vriezenveen +5 min
- Fri 20 Nov Max en route +5 min · last fix heading to Vriezenveen +5 min
- Sat 31 Oct Max en route +3 min · last fix heading to Vriezenveen +3 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 24
- 3–10 min 14% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 60% T n=5
- 100% W n=5
- 100% T n=2
- 50% F n=2
- 80% S n=5
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 28 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 |
|---|---|---|---|
| 17:25 | on time | +1 min | |
| 17:30 / 17:31 | ≈ on time | ≈ +2 min | |
| 17:33 | ≈ +1 min | ≈ +2 min | |
| 17:38 | ≈ +1 min | ≈ +3 min | |
| 17:43 | +1 min | +4 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Vriezenveen 17:52Partial coverage | 0 min | — |
| Fri 20 Nov | Vriezenveen 17:52 | +5 min | +5 min |
| Thu 19 Nov | Vriezenveen 17:48 | +2 min | +2 min |
| Wed 18 Nov | Vriezenveen 17:52 | 0 min | — |
| Tue 17 Nov | Vriezenveen 17:52 | +6 min | +6 min |
| Mon 16 Nov | Vriezenveen 17:52 | +1 min | +1 min |
| Sun 15 Nov | Vriezenveen 17:52Partial coverage | 0 min | — |
| Sat 14 Nov | Vriezenveen 17:49Partial coverage | 0 min | — |
| Fri 13 Nov | Vriezenveen 17:52 | +3 min | +3 min |
| Thu 12 Nov | Vriezenveen 17:52 | 0 min | — |
| Wed 11 Nov | Vriezenveen 17:52 | +1 min | +1 min |
| Tue 10 Nov | Vriezenveen 17:52 | +3 min | +3 min |
| Mon 9 Nov | Vriezenveen 17:52 | 0 min | — |
| Sun 8 Nov | Vriezenveen 17:52 | +1 min | +1 min |
| Sat 7 Nov | Vriezenveen 17:52 | +2 min | +2 min |
| Fri 6 Nov | Vriezenveen 17:52 | No data | — |
| Thu 5 Nov | Vriezenveen 17:52 | No data | — |
| Wed 4 Nov | Vriezenveen 17:52 | 0 min | — |
| Tue 3 Nov | Vriezenveen 17:52 | No data | — |
| Mon 2 Nov | Vriezenveen 17:52 | No data | — |
| Sun 1 Nov | Vriezenveen 17:52 | No data | — |
| Sat 31 Oct | Vriezenveen 17:52 | +3 min | +3 min |
| Fri 30 Oct | Vriezenveen 17:52 | No data | — |
| Thu 29 Oct | Vriezenveen 17:52 | No data | — |
| Wed 28 Oct | Vriezenveen 17:52 | 0 min | — |
| Tue 27 Oct | Vriezenveen 17:52 | 0 min | — |
| Mon 26 Oct | Vriezenveen 17:52 | No data | — |
| Sun 25 Oct | Vriezenveen 17:52 | No data | — |
| Sat 24 Oct | Vriezenveen 17:52 | No data | — |
| Fri 23 Oct | Vriezenveen 17:52 | No data | — |