Train Blauwnet A 31064 Mariënberg → Almelo

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

Blauwnet A 31064 Mariënberg–Almelo: final delay under 3 min on 11 of its 14 runs with data in the last 30 days (79%). 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 17:23 +3 min

  1. Mariënberg16:55
  2. Vroomshoop17:00
  3. Daarlerveen17:03
  4. Vriezenveen17:07
  5. Almelo17:13

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

Next departure 16:55 Monday · Mariënberg
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 7 full · 7 partial · 12 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 12 full · 7 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Thu 19 Nov Max en route +4 min · last fix heading to Vriezenveen +4 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Vriezenveen +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Vriezenveen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 16
  • 3–10 min 16% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 100% W n=4
  • 67% T n=3
  • 50% 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, 19 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:55on time +1 min
17:00≈ on time ≈ +3 min
17:03≈ on time ≈ +3 min
17:07≈ on time ≈ +3 min
17:13on time +3 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 17:23Partial coverage+3 min+3 min
Fri 20 NovVriezenveen 17:23Partial coverage0 min—
Thu 19 NovVriezenveen 17:23Partial coverage+4 min+4 min
Wed 18 NovVriezenveen 17:19Partial coverage0 min—
Tue 17 NovVriezenveen 17:19Partial coverage0 min—
Mon 16 NovVriezenveen 17:22Partial coverage0 min—
Sat 14 NovVriezenveen 17:22Partial coverage+1 min+1 min
Fri 13 NovVriezenveen 17:19No data—
Thu 12 NovVriezenveen 17:190 min—
Wed 11 NovVriezenveen 17:190 min—
Tue 10 NovVriezenveen 17:19No data—
Mon 9 NovVriezenveen 17:19+3 min+3 min
Sat 7 NovVriezenveen 17:19No data—
Fri 6 NovVriezenveen 17:24+4 min+4 min
Thu 5 NovVriezenveen 17:19No data—
Wed 4 NovVriezenveen 17:19No data—
Tue 3 NovVriezenveen 17:19No data—
Mon 2 NovVriezenveen 17:19No data—
Sat 31 OctVriezenveen 17:220 min—
Fri 30 OctVriezenveen 17:21No data—
Thu 29 OctVriezenveen 17:21No data—
Wed 28 OctVriezenveen 17:210 min—
Tue 27 OctVriezenveen 17:210 min—
Mon 26 OctVriezenveen 17:21No data—
Sat 24 OctVriezenveen 17:21No data—
Fri 23 OctVriezenveen 17:24No data—
Thu 22 OctVriezenveen 17:24No data—
Wed 21 OctVriezenveen 17:17No data—
Tue 20 OctVriezenveen 17:210 min—
Sat 17 OctVriezenveen 17:21No data—