Train Blauwnet A 31015 Almelo – Hardenberg

Almelo 07:18 → Hardenberg 07:42 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 6 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Mariënberg at 07:49 No data

  1. Almelo07:18
  2. Vriezenveen07:23
  3. Daarlerveen07:28
  4. Vroomshoop07:30
  5. Mariënberg07:36
  6. Hardenberg07:42

Next service: tomorrow 07:18 from Almelo · Fri 6 Nov

Next departure 07:18 tomorrow · Almelo
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 10 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 50 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

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 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
07:18on time on time
07:23— —
07:28— —
07:30 / 07:31— —
07:36— —
07:42— —

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 07:49No data—
Wed 4 NovMariënberg 07:49Partial coverage0 min—
Tue 3 NovMariënberg 07:49No data—
Mon 2 NovMariënberg 07:59No data—
Fri 30 OctMariënberg 07:50Partial coverage0 min—
Thu 29 OctMariënberg 07:50Partial coverage0 min—
Wed 28 OctMariënberg 07:50Partial coverage0 min—
Tue 27 OctMariënberg 07:50Partial coverage0 min—
Mon 26 OctMariënberg 07:50Partial coverage0 min—
Fri 23 OctMariënberg 07:50Partial coverage0 min—
Thu 22 OctMariënberg 07:50No data—
Wed 21 OctMariënberg 07:50No data—
Tue 20 OctMariënberg 07:50Partial coverage0 min—
Mon 19 OctMariënberg 07:51Partial coverage0 min—
Fri 16 OctMariënberg 07:50No data—
Thu 15 OctMariënberg 07:52No data—
Wed 14 OctMariënberg 07:50No data—
Tue 13 OctMariënberg 07:50No data—
Mon 12 OctMariënberg 07:50No data—
Fri 9 OctMariënberg 07:50Partial coverage0 min—
Thu 8 OctMariënberg 07:51Partial coverage+1 min+1 min
Wed 7 OctMariënberg 07:50Partial coverage+1 min+1 min
Tue 6 OctMariënberg 07:50Partial coverage0 min—
Mon 5 OctMariënberg 07:51No data—
Fri 2 OctMariënberg 07:50No data—
Thu 1 OctMariënberg 07:50No data—
Wed 30 SeptMariënberg 07:50No data—
Tue 29 SeptMariënberg 07:50No data—
Mon 28 SeptMariënberg 07:50No data—
Fri 25 SeptMariënberg 07:50No data—