Train Blauwnet A 31046 Mariënberg → Almelo

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

Blauwnet A 31046 Mariënberg–Almelo: final delay under 3 min on 15 of its 20 runs with data in the last 30 days (75%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 13:07 (GMT+1).

✓ Today’s run finished

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

  1. Mariënberg12:25
  2. Vroomshoop12:30
  3. Daarlerveen12:33
  4. Vriezenveen12:38
  5. Almelo12:43

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

Next departure 12:25 tomorrow · Mariënberg
On-time · 30 days
75%
15/20 runs under 3 min
RT coverage: 18 full · 2 partial · 10 no data
On-time · 90 days
81%
21/26 runs under 3 min
RT coverage: 24 full · 2 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Fri 13 Nov Max en route +5 min · last fix heading to Vriezenveen +5 min
  • Sat 24 Oct Max en route +5 min · last fix heading to Vriezenveen +5 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Vriezenveen +4 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Vriezenveen +4 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Vriezenveen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 21
  • 3–10 min 19% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=6
  • 75% W n=4
  • 67% T n=3
  • 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, 26 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
12:25on time on time
12:30 / 12:31≈ on time ≈ +1 min
12:33≈ on time ≈ +2 min
12:38≈ on time ≈ +3 min
12: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 12:52Partial coverage0 min—
Fri 20 NovVriezenveen 12:520 min—
Thu 19 NovVriezenveen 12:490 min—
Wed 18 NovVriezenveen 12:52+4 min+4 min
Tue 17 NovVriezenveen 12:52+1 min+1 min
Mon 16 NovVriezenveen 12:53+3 min+3 min
Sun 15 NovVriezenveen 12:53+2 min+2 min
Sat 14 NovVriezenveen 12:52Partial coverage0 min—
Fri 13 NovVriezenveen 12:52+5 min+5 min
Thu 12 NovVriezenveen 12:52+4 min+4 min
Wed 11 NovVriezenveen 12:520 min—
Tue 10 NovVriezenveen 12:520 min—
Mon 9 NovVriezenveen 12:52No data—
Sun 8 NovVriezenveen 12:54+3 min+3 min
Sat 7 NovVriezenveen 12:52No data—
Fri 6 NovVriezenveen 12:52No data—
Thu 5 NovVriezenveen 12:52No data—
Wed 4 NovVriezenveen 12:52No data—
Tue 3 NovVriezenveen 12:520 min—
Mon 2 NovVriezenveen 12:52No data—
Sun 1 NovVriezenveen 12:53+1 min+1 min
Sat 31 OctVriezenveen 12:520 min—
Fri 30 OctVriezenveen 12:52No data—
Thu 29 OctVriezenveen 12:520 min—
Wed 28 OctVriezenveen 12:520 min—
Tue 27 OctVriezenveen 12:520 min—
Mon 26 OctVriezenveen 12:52No data—
Sun 25 OctVriezenveen 12:52No data—
Sat 24 OctVriezenveen 12:55+5 min+5 min
Fri 23 OctVriezenveen 12:52No data—