Train Blauwnet A 31029 Almelo → Mariënberg

Almelo 10:48 → Mariënberg 11:06 Daily 0 h 18 min · 5 stops Blauwnet A

Blauwnet A 31029 Almelo–Mariënberg: final delay under 3 min on 18 of its 18 runs with data in the last 30 days (100%). 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 Vroomshoop at 11:14 0 min

  1. Almelo10:48
  2. Vriezenveen10:53
  3. Daarlerveen10:58
  4. Vroomshoop11:00
  5. Mariënberg11:06

Next service: tomorrow 10:48 from Almelo · Sun 22 Nov

Next departure 10:48 tomorrow · Almelo
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 13 full · 8 partial · 67 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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:48on time on time
10:53≈ on time ≈ on time
10:58≈ on time ≈ +1 min
11:00 / 11:01≈ on time ≈ +1 min
11:06on time +2 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 11:14Partial coverage0 min—
Fri 20 NovVroomshoop 11:14Partial coverage0 min—
Thu 19 NovVroomshoop 11:14Partial coverage0 min—
Wed 18 NovVroomshoop 11:14Partial coverage0 min—
Tue 17 NovVroomshoop 11:14Partial coverage0 min—
Mon 16 NovVroomshoop 11:18Partial coverage+3 min+3 min
Sun 15 NovVroomshoop 11:15Partial coverage0 min—
Sat 14 NovVroomshoop 11:14Partial coverage0 min—
Fri 13 NovMariënberg 11:19+1 min+1 min
Thu 12 NovMariënberg 11:22+2 min+2 min
Wed 11 NovMariënberg 11:22+1 min+1 min
Tue 10 NovMariënberg 11:190 min—
Mon 9 NovMariënberg 11:190 min—
Sun 8 NovMariënberg 11:19No data—
Sat 7 NovMariënberg 11:190 min—
Fri 6 NovMariënberg 11:22No data—
Thu 5 NovMariënberg 11:19No data—
Wed 4 NovMariënberg 11:22+2 min+2 min
Tue 3 NovMariënberg 11:19No data—
Mon 2 NovMariënberg 11:19No data—
Sun 1 NovMariënberg 11:20No data—
Sat 31 OctMariënberg 11:200 min—
Fri 30 OctMariënberg 11:20No data—
Thu 29 OctMariënberg 11:21No data—
Wed 28 OctMariënberg 11:200 min—
Tue 27 OctMariënberg 11:200 min—
Mon 26 OctMariënberg 11:21No data—
Sun 25 OctMariënberg 11:20No data—
Sat 24 OctMariënberg 11:20No data—
Fri 23 OctMariënberg 11:21No data—