Train Blauwnet A 31034 Hardenberg – Almelo

Hardenberg 09:16 → Almelo 09:43 Daily 0 h 27 min · 6 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Vriezenveen at 09:52 No data

  1. Hardenberg09:16
  2. Mariënberg09:23
  3. Vroomshoop09:30
  4. Daarlerveen09:33
  5. Vriezenveen09:38
  6. Almelo09:43

Next service: tomorrow 09:16 from Hardenberg · Fri 6 Nov

Next departure 09:16 tomorrow · Hardenberg
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 11 full · 6 partial · 13 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 12 full · 6 partial · 70 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: +2 min

Last 30 days

Arrival delay at Almelo, in minutes. One bar per run.

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

Worst days

  • Sun 11 Oct Max en route +4 min · last fix heading to Vriezenveen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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:16on time on time
09:23 / 09:25≈ on time ≈ +1 min
09:30 / 09:31≈ on time ≈ +2 min
09:33≈ on time ≈ +2 min
09:38≈ on time ≈ +2 min
09:43on 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
Thu 5 NovVriezenveen 09:52No data—
Wed 4 NovVriezenveen 09:53Partial coverage+1 min+1 min
Tue 3 NovVriezenveen 09:520 min—
Mon 2 NovVriezenveen 09:53Partial coverage0 min—
Sun 1 NovVriezenveen 09:53+2 min+2 min
Sat 31 OctVriezenveen 09:52No data—
Fri 30 OctVriezenveen 09:52No data—
Thu 29 OctVriezenveen 09:52Partial coverage0 min—
Wed 28 OctVriezenveen 09:52Partial coverage0 min—
Tue 27 OctVriezenveen 09:520 min—
Mon 26 OctVriezenveen 09:52No data—
Sun 25 OctVriezenveen 09:52No data—
Sat 24 OctVriezenveen 09:520 min—
Fri 23 OctVriezenveen 09:52Partial coverage0 min—
Thu 22 OctVriezenveen 09:52No data—
Wed 21 OctVriezenveen 09:53No data—
Tue 20 OctVriezenveen 09:540 min—
Mon 19 OctVriezenveen 09:52Partial coverage0 min—
Sun 18 OctVriezenveen 09:53+2 min+2 min
Sat 17 OctVriezenveen 09:52No data—
Fri 16 OctVriezenveen 09:52No data—
Thu 15 OctVriezenveen 09:52No data—
Wed 14 OctVriezenveen 09:52No data—
Tue 13 OctVriezenveen 09:520 min—
Mon 12 OctVriezenveen 09:53No data—
Sun 11 OctVriezenveen 09:52+4 min+4 min
Sat 10 OctVriezenveen 09:520 min—
Fri 9 OctVriezenveen 09:53No data—
Thu 8 OctVriezenveen 09:520 min—
Wed 7 OctVriezenveen 09:520 min—