Train Blauwnet A 31049 Almelo → Mariënberg

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

Blauwnet A 31049 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, 18:04 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Vroomshoop at 16:17 +1 min

  1. Almelo15:48
  2. Vriezenveen15:53
  3. Daarlerveen15:58
  4. Vroomshoop16:00
  5. Mariënberg16:06

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

Next departure 15: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%
25/25 runs under 3 min
RT coverage: 17 full · 8 partial · 63 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

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

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

Stops and timetable

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

Last 90 days, 25 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
15:48on time on time
15:53≈ on time ≈ on time
15:58≈ on time ≈ on time
16:00 / 16:01≈ on time ≈ on time
16:06on time on time

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:17Partial coverage+1 min+2 min
Fri 20 NovVroomshoop 16:14Partial coverage0 min—
Thu 19 NovVroomshoop 16:17Partial coverage+2 min+2 min
Wed 18 NovVroomshoop 16:14Partial coverage0 min—
Tue 17 NovVroomshoop 16:14Partial coverage0 min—
Mon 16 NovVroomshoop 16:15Partial coverage0 min—
Sun 15 NovVroomshoop 16:14Partial coverage0 min—
Sat 14 NovVroomshoop 16:14Partial coverage0 min—
Fri 13 NovMariënberg 16:190 min—
Thu 12 NovMariënberg 16:190 min—
Wed 11 NovMariënberg 16:19+1 min+1 min
Tue 10 NovMariënberg 16:190 min—
Mon 9 NovMariënberg 16:19No data—
Sun 8 NovMariënberg 16:20+1 min+1 min
Sat 7 NovMariënberg 16:19No data—
Fri 6 NovMariënberg 16:19No data—
Thu 5 NovMariënberg 16:20No data—
Wed 4 NovMariënberg 16:190 min—
Tue 3 NovMariënberg 16:19No data—
Mon 2 NovMariënberg 16:19No data—
Sun 1 NovMariënberg 16:210 min—
Sat 31 OctMariënberg 16:200 min—
Fri 30 OctMariënberg 16:20No data—
Thu 29 OctMariënberg 16:20No data—
Wed 28 OctMariënberg 16:200 min—
Tue 27 OctMariënberg 16:20No data—
Mon 26 OctMariënberg 16:20No data—
Sun 25 OctMariënberg 16:20No data—
Sat 24 OctMariënberg 16:200 min—
Fri 23 OctMariënberg 16:20No data—