Train Blauwnet A 31041 Almelo – Hardenberg

Almelo 13:48 → Hardenberg 14:12 Daily 0 h 24 min · 6 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Mariënberg at 14:19 No data

  1. Almelo13:48
  2. Vriezenveen13:53
  3. Daarlerveen13:58
  4. Vroomshoop14:00
  5. Mariënberg14:06
  6. Hardenberg14:12

Next service: tomorrow 13:48 from Almelo · Mon 9 Nov

Next departure 13:48 tomorrow · Almelo
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 21 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 75 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 Hardenberg, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +5 min · last fix heading to Mariënberg +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 50% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 13 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:48on time on time
13:53— —
13:58— —
14:00 / 14:01— —
14:06— —
14:12— —

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
Sun 8 NovMariënberg 14:19No data—
Sat 7 NovMariënberg 14:19Partial coverage0 min—
Fri 6 NovMariënberg 14:19No data—
Thu 5 NovMariënberg 14:19No data—
Wed 4 NovMariënberg 14:19Partial coverage0 min—
Tue 3 NovMariënberg 14:24No data—
Mon 2 NovMariënberg 14:19No data—
Sun 1 NovMariënberg 14:21Partial coverage0 min—
Sat 31 OctMariënberg 14:20No data—
Fri 30 OctMariënberg 14:20No data—
Thu 29 OctMariënberg 14:20No data—
Wed 28 OctMariënberg 14:20Partial coverage0 min—
Tue 27 OctMariënberg 14:20No data—
Mon 26 OctMariënberg 14:20No data—
Sun 25 OctMariënberg 14:20No data—
Sat 24 OctMariënberg 14:20Partial coverage0 min—
Fri 23 OctMariënberg 14:20No data—
Thu 22 OctMariënberg 14:20No data—
Wed 21 OctMariënberg 14:20No data—
Tue 20 OctMariënberg 14:20Partial coverage0 min—
Mon 19 OctMariënberg 14:20Partial coverage0 min—
Sun 18 OctMariënberg 14:21No data—
Sat 17 OctMariënberg 14:20No data—
Fri 16 OctMariënberg 14:20No data—
Thu 15 OctMariënberg 14:20No data—
Wed 14 OctMariënberg 14:20No data—
Tue 13 OctMariënberg 14:20No data—
Mon 12 OctMariënberg 14:21No data—
Sun 11 OctMariënberg 14:22Partial coverage+3 min+3 min
Sat 10 OctMariënberg 14:20Partial coverage0 min—