Train Blauwnet A 31053 Almelo → Mariënberg

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

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

✓ Today’s run finished

Today, last fix heading to Vroomshoop at 17:15 0 min

  1. Almelo16:48
  2. Vriezenveen16:53
  3. Daarlerveen16:58
  4. Vroomshoop17:00
  5. Mariënberg17:06

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

Next departure 16:48 tomorrow · Almelo
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 17 full · 3 partial · 10 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 26 full · 3 partial · 59 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

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

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

On-time by weekday

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

Stops and timetable

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

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