Train Blauwnet A 31017 Almelo → Mariënberg

Almelo 07:48 → Mariënberg 08:06 Mon, Tue, Wed, Thu, Fri, Sat 0 h 18 min · 5 stops Blauwnet A

Blauwnet A 31017 Almelo–Mariënberg: final delay under 3 min on 16 of its 16 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 13:06 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Vroomshoop at 08:14 No data

  1. Almelo07:48
  2. Vriezenveen07:53
  3. Daarlerveen07:58
  4. Vroomshoop08:00
  5. Mariënberg08:06

Next service: Monday 07:48 from Almelo · Mon 23 Nov

Next departure 07:48 Monday · Almelo
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 10 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 54 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: +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

Worst days

  • Fri 9 Oct Max en route +5 min · last fix heading to Mariënberg +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 67% F n=3
  • 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, 23 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
07:48on time on time
07:53≈ on time ≈ +1 min
07:58≈ on time ≈ +1 min
08:00 / 08:01≈ on time ≈ +1 min
08:06on 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 08:14Partial coverageNo data—
Fri 20 NovVroomshoop 08:140 min—
Thu 19 NovVroomshoop 08:14+1 min—
Wed 18 NovVroomshoop 08:14+1 min+1 min
Tue 17 NovVroomshoop 08:140 min—
Mon 16 NovVroomshoop 08:140 min—
Sat 14 NovVroomshoop 08:14Partial coverage0 min—
Fri 13 NovMariënberg 08:190 min—
Thu 12 NovMariënberg 08:23+2 min+2 min
Wed 11 NovMariënberg 08:190 min—
Tue 10 NovMariënberg 08:19+2 min+2 min
Mon 9 NovMariënberg 08:19+1 min+1 min
Sat 7 NovMariënberg 08:190 min—
Fri 6 NovMariënberg 08:19No data—
Thu 5 NovMariënberg 08:19No data—
Wed 4 NovMariënberg 08:19+1 min+1 min
Tue 3 NovMariënberg 08:19No data—
Mon 2 NovMariënberg 08:19No data—
Sat 31 OctMariënberg 08:20No data—
Fri 30 OctMariënberg 08:20No data—
Thu 29 OctMariënberg 08:20No data—
Wed 28 OctMariënberg 08:200 min—
Tue 27 OctMariënberg 08:200 min—
Mon 26 OctMariënberg 08:22+1 min+1 min
Sat 24 OctMariënberg 08:20No data—
Fri 23 OctMariënberg 08:20No data—
Thu 22 OctMariënberg 08:20No data—
Wed 21 OctMariënberg 08:20No data—
Tue 20 OctMariënberg 08:210 min—
Mon 19 OctMariënberg 08:210 min—