Train Blauwnet A 31051 Almelo → Mariënberg

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

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

✓ Today’s run finished

Today, last fix heading to Vroomshoop at 16:48 +4 min

  1. Almelo16:17
  2. Vriezenveen16:22
  3. Daarlerveen16:26
  4. Vroomshoop16:29
  5. Mariënberg16:36

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

Next departure 16:17 Monday · Almelo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 12 full · 7 partial · 7 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 20 full · 7 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Worst days

  • Sat 21 Nov Max en route +5 min · last fix heading to Vroomshoop +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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