Train Blauwnet A 31052 Mariënberg → Almelo

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

Blauwnet A 31052 Mariënberg–Almelo: final delay under 3 min on 17 of its 17 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 Vriezenveen at 14:22 0 min

  1. Mariënberg13:55
  2. Vroomshoop14:00
  3. Daarlerveen14:03
  4. Vriezenveen14:08
  5. Almelo14:13

Next service: Monday 13:55 from Mariënberg · Mon 23 Nov

Next departure 13:55 Monday · Mariënberg
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 10 full · 7 partial · 9 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 13 full · 7 partial · 56 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 Almelo, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=6
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
13:55on time on time
14:00≈ on time ≈ on time
14:03≈ on time ≈ on time
14:08≈ on time ≈ +1 min
14:13on 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 NovVriezenveen 14:22Partial coverage0 min—
Fri 20 NovVriezenveen 14:22Partial coverage0 min—
Thu 19 NovVriezenveen 14:22Partial coverage0 min—
Wed 18 NovVriezenveen 14:22Partial coverage0 min—
Tue 17 NovVriezenveen 14:22Partial coverage+2 min+2 min
Mon 16 NovVriezenveen 14:23Partial coverage0 min—
Sat 14 NovVriezenveen 14:22Partial coverage+1 min+1 min
Fri 13 NovVriezenveen 14:22+1 min+1 min
Thu 12 NovVriezenveen 14:220 min—
Wed 11 NovVriezenveen 14:22+1 min+1 min
Tue 10 NovVriezenveen 14:220 min—
Mon 9 NovVriezenveen 14:22No data—
Sat 7 NovVriezenveen 14:22No data—
Fri 6 NovVriezenveen 14:22No data—
Thu 5 NovVriezenveen 14:22No data—
Wed 4 NovVriezenveen 14:22No data—
Tue 3 NovVriezenveen 14:240 min—
Mon 2 NovVriezenveen 14:220 min—
Sat 31 OctVriezenveen 14:22No data—
Fri 30 OctVriezenveen 14:22No data—
Thu 29 OctVriezenveen 14:220 min—
Wed 28 OctVriezenveen 14:220 min—
Tue 27 OctVriezenveen 14:220 min—
Mon 26 OctVriezenveen 14:22No data—
Sat 24 OctVriezenveen 14:220 min—
Fri 23 OctVriezenveen 14:22No data—
Thu 22 OctVriezenveen 14:22No data—
Wed 21 OctVriezenveen 14:22No data—
Tue 20 OctVriezenveen 14:230 min—
Sat 17 OctVriezenveen 14:22No data—