Train Blauwnet A 31043 Almelo → Mariënberg

Almelo 14:17 → Mariënberg 14:36 Mon, Tue, Wed, Thu, Fri, Sat 0 h 19 min · 5 stops Blauwnet A

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

✓ Today’s run finished

Today, last fix heading to Vroomshoop at 14:44 0 min

  1. Almelo14:17
  2. Vriezenveen14:22
  3. Daarlerveen14:26
  4. Vroomshoop14:29
  5. Mariënberg14:36

Next service: Monday 14:17 from Almelo · Mon 23 Nov

Next departure 14:17 Monday · Almelo
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 8 full · 7 partial · 11 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 15 full · 7 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Mariënberg, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
14:17on time on time
14:22≈ on time ≈ +1 min
14:26≈ on time ≈ +1 min
14:29 / 14:30≈ on time ≈ +1 min
14:36on time +1 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 NovVroomshoop 14:44Partial coverage0 min—
Fri 20 NovVroomshoop 14:44Partial coverage0 min—
Thu 19 NovVroomshoop 14:44Partial coverage0 min—
Wed 18 NovVroomshoop 14:44Partial coverage0 min—
Tue 17 NovVroomshoop 14:44Partial coverage+1 min—
Mon 16 NovVroomshoop 14:45Partial coverage0 min—
Sat 14 NovVroomshoop 14:44Partial coverage+1 min+1 min
Fri 13 NovMariënberg 14:490 min—
Thu 12 NovMariënberg 14:490 min—
Wed 11 NovMariënberg 14:49+1 min+1 min
Tue 10 NovMariënberg 14:52+3 min+3 min
Mon 9 NovMariënberg 14:490 min—
Sat 7 NovMariënberg 14:49No data—
Fri 6 NovMariënberg 14:49No data—
Thu 5 NovMariënberg 14:49No data—
Wed 4 NovMariënberg 14:490 min—
Tue 3 NovMariënberg 14:49No data—
Mon 2 NovMariënberg 14:49No data—
Sat 31 OctMariënberg 14:49No data—
Fri 30 OctMariënberg 14:50No data—
Thu 29 OctMariënberg 14:49No data—
Wed 28 OctMariënberg 14:500 min—
Tue 27 OctMariënberg 14:490 min—
Mon 26 OctMariënberg 14:49No data—
Sat 24 OctMariënberg 14:49No data—
Fri 23 OctMariënberg 14:50No data—
Thu 22 OctMariënberg 14:52No data—
Wed 21 OctMariënberg 14:49No data—
Tue 20 OctMariënberg 14:500 min—
Sat 17 OctMariënberg 14:50No data—