Train Blauwnet A 31055 Almelo → Mariënberg

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

Blauwnet A 31055 Almelo–Mariënberg: final delay under 3 min on 16 of its 18 runs with data in the last 30 days (89%). 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 17:44 +5 min

  1. Almelo17:18
  2. Vriezenveen17:23
  3. Daarlerveen17:28
  4. Vroomshoop17:30
  5. Mariënberg17:36

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

Next departure 17:18 Monday · Almelo
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 11 full · 7 partial · 8 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 19 full · 7 partial · 50 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: +3 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 +5 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Mariënberg +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=4
  • 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, 26 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
17:18on time on time
17:23≈ on time ≈ +1 min
17:28≈ on time ≈ +1 min
17:30 / 17:31≈ on time ≈ +1 min
17:36on 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 17:44Partial coverage+5 min+5 min
Fri 20 NovVroomshoop 17:44Partial coverage+1 min—
Thu 19 NovVroomshoop 17:44Partial coverage+1 min+1 min
Wed 18 NovVroomshoop 17:44Partial coverage0 min—
Tue 17 NovVroomshoop 17:44Partial coverage0 min—
Mon 16 NovVroomshoop 17:45Partial coverage0 min—
Sat 14 NovVroomshoop 17:45Partial coverage0 min—
Fri 13 NovMariënberg 17:490 min—
Thu 12 NovMariënberg 17:490 min—
Wed 11 NovMariënberg 17:490 min—
Tue 10 NovMariënberg 17:49+4 min+4 min
Mon 9 NovMariënberg 17:490 min—
Sat 7 NovMariënberg 17:49+2 min+2 min
Fri 6 NovMariënberg 17:490 min—
Thu 5 NovMariënberg 17:49No data—
Wed 4 NovMariënberg 17:490 min—
Tue 3 NovMariënberg 17:49No data—
Mon 2 NovMariënberg 17:49No data—
Sat 31 OctMariënberg 17:50+1 min+1 min
Fri 30 OctMariënberg 17:51No data—
Thu 29 OctMariënberg 17:50No data—
Wed 28 OctMariënberg 17:500 min—
Tue 27 OctMariënberg 17:500 min—
Mon 26 OctMariënberg 17:50No data—
Sat 24 OctMariënberg 17:50No data—
Fri 23 OctMariënberg 17:50No data—
Thu 22 OctMariënberg 17:44No data—
Wed 21 OctMariënberg 17:50No data—
Tue 20 OctMariënberg 17:500 min—
Sat 17 OctMariënberg 17:50No data—