Train Blauwnet A 31049 Almelo – Hardenberg

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

Running now · updated 16:01

Heading to Hardenberg No data

Estimated arrival at Hardenberg 16:12 · 63 km/h

  1. Almelo15:48
  2. Vriezenveen15:53
  3. Daarlerveen15:58
  4. Vroomshoop16:00
  5. Mariënberg16:06
  6. Hardenberg16:12
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 20 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 76 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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