Train Blauwnet A 31038 Mariënberg → Almelo

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

Blauwnet A 31038 Mariënberg–Almelo: final delay under 3 min on 13 of its 17 runs with data in the last 30 days (76%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 13:08 (GMT+1).

✓ Today’s run finished

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

  1. Mariënberg10:25
  2. Vroomshoop10:30
  3. Daarlerveen10:33
  4. Vriezenveen10:38
  5. Almelo10:43

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

Next departure 10:25 tomorrow · Mariënberg
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 9 full · 8 partial · 13 no data
On-time · 90 days
83%
20/24 runs under 3 min
RT coverage: 16 full · 8 partial · 64 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 1 Nov Max en route +5 min · last fix heading to Vriezenveen +5 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Vriezenveen +3 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Vriezenveen +3 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Vriezenveen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 20
  • 3–10 min 17% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=5
  • 75% W n=4
  • 67% T n=3
  • 100% F n=3
  • 100% S n=2
  • 75% S n=4

Stops and timetable

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

Last 90 days, 24 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
10:25on time +1 min
10:30 / 10:31≈ on time ≈ +2 min
10:33≈ on time ≈ +2 min
10:38≈ on time ≈ +2 min
10:43+1 min +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

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