Train Blauwnet K 7907 Almelo – Enschede

Almelo 05:30 → Enschede 05:56 Mon, Tue, Wed, Thu, Fri 0 h 26 min · 6 stops Blauwnet K

It does not run today

Last recorded run: Friday 13 November +3 min

Next service: Monday 05:30 from Almelo · Mon 16 Nov

Full trip card
Next departure 05:30 Monday · Almelo
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 8 full · 10 partial · 3 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 11 full · 13 partial · 40 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 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

  • Thu 5 Nov Max en route +4 min · last fix heading to Enschede Kennispark +4 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Enschede Kennispark +3 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=4
  • 100% T n=5
  • 100% W n=5
  • 83% T n=6
  • 75% F n=4
  • — S n=0
  • — S n=0

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
05:30on time on time
Almelo de Riet
05:33≈ on time ≈ on time
Borne
05:38≈ on time ≈ +1 min
Hengelo
05:43 / 05:47≈ +1 min ≈ +1 min
Enschede Kennispark
05:51≈ +1 min ≈ +2 min
Enschede
05:56+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
Fri 13 NovEnschede Kennispark 06:07Partial coverage+3 min+3 min
Thu 12 NovEnschede Kennispark 06:04+1 min—
Wed 11 NovEnschede Kennispark 06:040 min—
Tue 10 NovEnschede Kennispark 06:05Partial coverage+2 min+2 min
Mon 9 NovEnschede Kennispark 06:04Partial coverage+2 min+2 min
Fri 6 NovEnschede Kennispark 06:04No data—
Thu 5 NovEnschede Kennispark 06:08+4 min+4 min
Wed 4 NovEnschede Kennispark 06:04+3 min+3 min
Tue 3 NovEnschede Kennispark 06:04Partial coverage+2 min+2 min
Mon 2 NovEnschede Kennispark 06:04No data—
Fri 30 OctEnschede Kennispark 06:06Partial coverage+1 min+1 min
Thu 29 OctEnschede Kennispark 06:060 min—
Wed 28 OctEnschede Kennispark 06:05+1 min+1 min
Tue 27 OctEnschede Kennispark 06:06Partial coverage+1 min+1 min
Mon 26 OctEnschede Kennispark 06:05Partial coverage0 min—
Fri 23 OctEnschede Kennispark 06:06Partial coverage+3 min+3 min
Thu 22 OctEnschede Kennispark 06:06+1 min—
Wed 21 OctEnschede Kennispark 06:06+3 min+3 min
Tue 20 OctEnschede Kennispark 06:06Partial coverage+3 min+3 min
Mon 19 OctEnschede Kennispark 06:06Partial coverage+3 min+3 min
Fri 16 OctEnschede Kennispark 06:06No data—
Thu 15 OctEnschede Kennispark 06:07+2 min+2 min
Wed 14 OctEnschede Kennispark 06:05No data—
Tue 13 OctEnschede Kennispark 06:05No data—
Mon 12 OctEnschede Kennispark 06:06Partial coverage+1 min+1 min
Fri 9 OctEnschede Kennispark 06:05Partial coverage+1 min+1 min
Thu 8 OctEnschede Kennispark 06:06+1 min+1 min
Wed 7 OctEnschede Kennispark 06:06+1 min+1 min
Tue 6 OctEnschede Kennispark 06:07Partial coverage+2 min+2 min
Mon 5 OctEnschede Kennispark 06:07No data—