Train Blauwnet A 31066 Mariënberg → Almelo

Mariënberg 17:25 → Almelo 17:43 Daily 0 h 18 min · 5 stops Blauwnet A

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).

✓ Today’s run finished

Today, last fix heading to Vriezenveen at 17:52 0 min

  1. Mariënberg17:25
  2. Vroomshoop17:30
  3. Daarlerveen17:33
  4. Vriezenveen17:38
  5. Almelo17:43

Next service: tomorrow 17:25 from Mariënberg · Sun 22 Nov

Next departure 17:25 tomorrow · Mariënberg
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 16 full · 3 partial · 11 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 25 full · 3 partial · 59 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

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.

StopSched.Usually 9 days in 10
17:25on 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

DateLast stopFinalMax
Sat 21 NovVriezenveen 17:52Partial coverage0 min—
Fri 20 NovVriezenveen 17:52+5 min+5 min
Thu 19 NovVriezenveen 17:48+2 min+2 min
Wed 18 NovVriezenveen 17:520 min—
Tue 17 NovVriezenveen 17:52+6 min+6 min
Mon 16 NovVriezenveen 17:52+1 min+1 min
Sun 15 NovVriezenveen 17:52Partial coverage0 min—
Sat 14 NovVriezenveen 17:49Partial coverage0 min—
Fri 13 NovVriezenveen 17:52+3 min+3 min
Thu 12 NovVriezenveen 17:520 min—
Wed 11 NovVriezenveen 17:52+1 min+1 min
Tue 10 NovVriezenveen 17:52+3 min+3 min
Mon 9 NovVriezenveen 17:520 min—
Sun 8 NovVriezenveen 17:52+1 min+1 min
Sat 7 NovVriezenveen 17:52+2 min+2 min
Fri 6 NovVriezenveen 17:52No data—
Thu 5 NovVriezenveen 17:52No data—
Wed 4 NovVriezenveen 17:520 min—
Tue 3 NovVriezenveen 17:52No data—
Mon 2 NovVriezenveen 17:52No data—
Sun 1 NovVriezenveen 17:52No data—
Sat 31 OctVriezenveen 17:52+3 min+3 min
Fri 30 OctVriezenveen 17:52No data—
Thu 29 OctVriezenveen 17:52No data—
Wed 28 OctVriezenveen 17:520 min—
Tue 27 OctVriezenveen 17:520 min—
Mon 26 OctVriezenveen 17:52No data—
Sun 25 OctVriezenveen 17:52No data—
Sat 24 OctVriezenveen 17:52No data—
Fri 23 OctVriezenveen 17:52No data—