Train Blauwnet A 31039 Almelo → Mariënberg

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

Blauwnet A 31039 Almelo–Mariënberg: final delay under 3 min on 16 of its 16 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 13:44 0 min

  1. Almelo13:18
  2. Vriezenveen13:23
  3. Daarlerveen13:28
  4. Vroomshoop13:30
  5. Mariënberg13:36

Next service: Monday 13:18 from Almelo · Mon 23 Nov

Next departure 13:18 Monday · Almelo
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 14 full · 2 partial · 10 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 56 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • — S n=0

Stops and timetable

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

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