Train Blauwnet K 7913 Almelo – Enschede

Almelo 07:00 → Enschede 07:27 Mon, Tue, Wed, Thu, Fri, Sat 0 h 27 min · 6 stops Blauwnet K

It does not run today

Last recorded run: Saturday 14 November +8 min

Next service: tomorrow 07:00 from Almelo · Mon 16 Nov

Next departure 07:00 tomorrow · Almelo
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 17 full · 4 partial · 3 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 25 full · 5 partial · 45 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 14 Nov Max en route +8 min · last fix heading to Enschede Kennispark +8 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Enschede Kennispark +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Enschede Kennispark +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 27
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=6
  • 80% W n=5
  • 100% T n=4
  • 100% F n=5
  • 80% S n=5
  • — S n=0

Stops and timetable

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

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