Train Blauwnet A 31025 Almelo – Hardenberg

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

✓ Today’s run finished

Today, last fix heading to Mariënberg at 10:22 No data

  1. Almelo09:48
  2. Vriezenveen09:53
  3. Daarlerveen09:58
  4. Vroomshoop10:00
  5. Mariënberg10:06
  6. Hardenberg10:12

Next service: tomorrow 09:48 from Almelo · Fri 6 Nov

Next departure 09:48 tomorrow · Almelo
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 17 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 74 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 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
09:48on time on time
09:53— —
09:58— —
10:00 / 10:01— —
10:06— —
10: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
Thu 5 NovMariënberg 10:22No data—
Wed 4 NovMariënberg 10:19Partial coverage0 min—
Tue 3 NovMariënberg 10:19No data—
Mon 2 NovMariënberg 10:19No data—
Sun 1 NovMariënberg 10:20Partial coverage0 min—
Sat 31 OctMariënberg 10:21Partial coverage+1 min+1 min
Fri 30 OctMariënberg 10:23No data—
Thu 29 OctMariënberg 10:20No data—
Wed 28 OctMariënberg 10:20Partial coverage0 min—
Tue 27 OctMariënberg 10:20Partial coverage0 min—
Mon 26 OctMariënberg 10:20No data—
Sun 25 OctMariënberg 10:20No data—
Sat 24 OctMariënberg 10:20Partial coverage0 min—
Fri 23 OctMariënberg 10:20No data—
Thu 22 OctMariënberg 10:21No data—
Wed 21 OctMariënberg 10:20No data—
Tue 20 OctMariënberg 10:22Partial coverage0 min—
Mon 19 OctMariënberg 10:21No data—
Sun 18 OctMariënberg 10:20Partial coverage0 min—
Sat 17 OctMariënberg 10:20Partial coverage0 min—
Fri 16 OctMariënberg 10:20No data—
Thu 15 OctMariënberg 10:20No data—
Wed 14 OctMariënberg 10:22No data—
Tue 13 OctMariënberg 10:20No data—
Mon 12 OctMariënberg 10:20No data—
Sun 11 OctMariënberg 10:20Partial coverage0 min—
Sat 10 OctMariënberg 10:20No data—
Fri 9 OctMariënberg 10:24Partial coverage+4 min+4 min
Thu 8 OctMariënberg 10:20Partial coverage0 min—
Wed 7 OctMariënberg 10:21Partial coverage+1 min—