Train Blauwnet K 7917 Almelo – Enschede

Almelo 08:00 → Enschede 08:27 Daily 0 h 27 min · 6 stops Blauwnet K

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 08:00 from Almelo · Mon 9 Nov

Full trip card
Next departure 08:00 today · Almelo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 8 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 20 full · 4 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to Enschede Kennispark +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Enschede Kennispark +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
Almelo
08:00on time on time
Almelo de Riet
08:03≈ on time ≈ on time
Borne
08:08≈ on time ≈ +1 min
Hengelo
08:13 / 08:18≈ on time ≈ +1 min
Enschede Kennispark
08:22≈ on time ≈ +3 min
Enschede
08:27on time +3 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
Sun 8 NovEnschede Kennispark 08:37Partial coverage+1 min—
Sat 7 NovEnschede Kennispark 08:340 min—
Fri 6 NovEnschede Kennispark 08:34No data—
Thu 5 NovEnschede Kennispark 08:39No data—
Wed 4 NovEnschede Kennispark 08:39+5 min+5 min
Tue 3 NovEnschede Kennispark 08:38No data—
Mon 2 NovEnschede Kennispark 08:38No data—
Sun 1 NovEnschede Kennispark 08:37Partial coverage0 min—
Sat 31 OctEnschede Kennispark 08:360 min—
Fri 30 OctEnschede Kennispark 08:370 min—
Thu 29 OctEnschede Kennispark 08:360 min—
Wed 28 OctEnschede Kennispark 08:370 min—
Tue 27 OctEnschede Kennispark 08:380 min—
Mon 26 OctEnschede Kennispark 08:390 min—
Sat 24 OctWierden 08:07+2 min+2 min
Fri 23 OctEnschede Kennispark 08:400 min—
Thu 22 OctEnschede Kennispark 08:35No data—
Wed 21 OctEnschede Kennispark 08:38No data—
Tue 20 OctEnschede Kennispark 08:38+2 min+2 min
Mon 19 OctEnschede Kennispark 08:370 min—
Sun 18 OctEnschede Kennispark 08:36Partial coverage0 min—
Sat 17 OctEnschede Kennispark 08:370 min—
Fri 16 OctEnschede Kennispark 08:36No data—
Thu 15 OctEnschede Kennispark 08:360 min—
Tue 13 OctEnschede Kennispark 08:36No data—
Mon 12 OctEnschede Kennispark 08:360 min—
Sun 11 OctEnschede Kennispark 08:37Partial coverage0 min—
Sat 10 OctEnschede Kennispark 08:360 min—
Fri 9 OctEnschede Kennispark 08:360 min+1 min
Thu 8 OctEnschede Kennispark 08:38+3 min+3 min