Train Blauwnet A 31034 Mariënberg → Almelo
Blauwnet A 31034 Mariënberg–Almelo: final delay under 3 min on 20 of its 22 runs with data in the last 30 days (91%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 13:07 (GMT+1).
An alert on this phone or computer when the 31034 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 09:52 0 min
- Mariënberg09:25
- Vroomshoop09:30
- Daarlerveen09:34
- Vriezenveen09:38
- Almelo09:43
Next service: tomorrow 09: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
- Mon 16 Nov Max en route +9 min · last fix heading to Vriezenveen +9 min
- Sun 11 Oct Max en route +4 min · last fix heading to Vriezenveen +4 min
- Tue 17 Nov Max en route +3 min · last fix heading to Vriezenveen +3 min
Distribution · 90 days
31 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 28
- 3–10 min 10% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 86% T n=7
- 100% W n=5
- 100% T n=4
- 100% F n=3
- 100% S n=4
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 31 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 |
|---|---|---|---|
| 09:25 | on time | on time | |
| 09:30 / 09:31 | ≈ on time | ≈ +1 min | |
| 09:34 | ≈ on time | ≈ +2 min | |
| 09:38 | ≈ on time | ≈ +2 min | |
| 09:43 | on time | +3 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 09:52Partial coverage | 0 min | — |
| Fri 20 Nov | Vriezenveen 09:52 | 0 min | — |
| Thu 19 Nov | Vriezenveen 09:53 | +1 min | +1 min |
| Wed 18 Nov | Vriezenveen 09:52 | +2 min | +2 min |
| Tue 17 Nov | Vriezenveen 09:52 | +3 min | +3 min |
| Mon 16 Nov | Vriezenveen 09:53 | +9 min | +9 min |
| Sun 15 Nov | Vriezenveen 09:53Partial coverage | +2 min | +2 min |
| Sat 14 Nov | Vriezenveen 09:52Partial coverage | +1 min | +1 min |
| Fri 13 Nov | Vriezenveen 09:52 | 0 min | — |
| Thu 12 Nov | Vriezenveen 09:52 | 0 min | — |
| Wed 11 Nov | Vriezenveen 09:53 | +1 min | +1 min |
| Tue 10 Nov | Vriezenveen 09:52 | 0 min | — |
| Mon 9 Nov | Vriezenveen 09:52 | No data | — |
| Sun 8 Nov | Vriezenveen 09:52 | 0 min | — |
| Sat 7 Nov | Vriezenveen 09:52 | No data | — |
| Fri 6 Nov | Vriezenveen 09:52 | No data | — |
| Thu 5 Nov | Vriezenveen 09:52 | No data | — |
| Wed 4 Nov | Vriezenveen 09:53 | +1 min | +1 min |
| Tue 3 Nov | Vriezenveen 09:52 | 0 min | — |
| Mon 2 Nov | Vriezenveen 09:53 | 0 min | — |
| Sun 1 Nov | Vriezenveen 09:53 | +2 min | +2 min |
| Sat 31 Oct | Vriezenveen 09:52 | No data | — |
| Fri 30 Oct | Vriezenveen 09:52 | No data | — |
| Thu 29 Oct | Vriezenveen 09:52 | 0 min | — |
| Wed 28 Oct | Vriezenveen 09:52 | 0 min | — |
| Tue 27 Oct | Vriezenveen 09:52 | 0 min | — |
| Mon 26 Oct | Vriezenveen 09:52 | No data | — |
| Sun 25 Oct | Vriezenveen 09:52 | No data | — |
| Sat 24 Oct | Vriezenveen 09:52 | 0 min | — |
| Fri 23 Oct | Vriezenveen 09:52 | 0 min | — |