Train Blauwnet A 31062 Mariënberg → Almelo

Mariënberg 16:25 → Almelo 16:43 Daily 0 h 18 min · 5 stops Blauwnet A

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

✓ Today’s run finished

Today, last fix heading to Vriezenveen at 16:53 +2 min

  1. Mariënberg16:25
  2. Vroomshoop16:30
  3. Daarlerveen16:33
  4. Vriezenveen16:38
  5. Almelo16:43

Next service: tomorrow 16:25 from Mariënberg · Sun 22 Nov

Next departure 16:25 tomorrow · Mariënberg
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 10 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 23 full · 3 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 +3 min · last fix heading to Vriezenveen +3 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 96% · 25
  • 3–10 min 4% · 1
  • 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
  • 50% T n=2
  • 100% F n=2
  • 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, 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
16:25on time +1 min
16:30 / 16:31≈ on time ≈ +1 min
16:33≈ on time ≈ +1 min
16:38≈ on time ≈ +2 min
16:43on 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 NovVriezenveen 16:53Partial coverage+2 min+2 min
Fri 20 NovVriezenveen 16:520 min—
Thu 19 NovVriezenveen 16:53+3 min+3 min
Wed 18 NovVriezenveen 16:520 min—
Tue 17 NovVriezenveen 16:53+2 min+2 min
Mon 16 NovVriezenveen 16:54+3 min+3 min
Sun 15 NovVriezenveen 16:52Partial coverage0 min—
Sat 14 NovVriezenveen 16:52Partial coverage+1 min+1 min
Fri 13 NovVriezenveen 16:520 min—
Thu 12 NovVriezenveen 16:520 min—
Wed 11 NovVriezenveen 16:520 min—
Tue 10 NovVriezenveen 16:520 min—
Mon 9 NovVriezenveen 16:52+1 min+1 min
Sun 8 NovVriezenveen 16:53+2 min+2 min
Sat 7 NovVriezenveen 16:52+2 min+2 min
Fri 6 NovVriezenveen 16:54No data—
Thu 5 NovVriezenveen 16:52No data—
Wed 4 NovVriezenveen 16:520 min—
Tue 3 NovVriezenveen 16:52No data—
Mon 2 NovVriezenveen 16:52No data—
Sun 1 NovVriezenveen 16:52+1 min+1 min
Sat 31 OctVriezenveen 16:52+1 min+1 min
Fri 30 OctVriezenveen 16:52No data—
Thu 29 OctVriezenveen 16:52No data—
Wed 28 OctVriezenveen 16:480 min—
Tue 27 OctVriezenveen 16:520 min—
Mon 26 OctVriezenveen 16:54No data—
Sun 25 OctVriezenveen 16:52No data—
Sat 24 OctVriezenveen 16:52No data—
Fri 23 OctVriezenveen 16:52No data—