Train Blauwnet K 7947 Zwolle – Enschede

Zwolle 14:52 → Enschede 15:56 Daily 1 h 04 min · 11 stops Blauwnet K

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:52 from Zwolle · Fri 6 Nov

Next departure 14:52 today · Zwolle
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 2 full · 11 partial · 16 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 2 full · 13 partial · 73 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: +1 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

  • Mon 5 Oct Max en route +6 min · last fix heading to Enschede Kennispark +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 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 (11 stops).

Last 90 days, 15 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
14:52on time on time
14:59 / 15:01— —
15:05 / 15:09— —
15:16 / 15:19— —
15:25— —
15:29 / 15:30— —
15:33— —
15:38— —
15:43 / 15:47— —
15:51— —
15:56— —

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 NovEnschede Kennispark 16:05No data—
Wed 4 NovEnschede Kennispark 16:07Partial coverage+1 min+2 min
Tue 3 NovEnschede Kennispark 16:04No data—
Mon 2 NovEnschede Kennispark 16:04No data—
Sun 1 NovEnschede Kennispark 16:06Partial coverage0 min—
Sat 31 OctRaalte 15:23Partial coverageNo data—
Fri 30 OctEnschede Kennispark 16:05No data—
Thu 29 OctEnschede Kennispark 16:06Partial coverage0 min—
Wed 28 OctEnschede Kennispark 16:05Partial coverage0 min—
Tue 27 OctEnschede Kennispark 16:05No data—
Mon 26 OctEnschede Kennispark 16:07No data—
Sun 25 OctWierden 15:41No data—
Sat 24 OctWierden 15:36+1 min+1 min
Fri 23 OctEnschede Kennispark 16:06No data—
Thu 22 OctEnschede Kennispark 16:05No data—
Wed 21 OctEnschede Kennispark 16:05No data—
Tue 20 OctEnschede Kennispark 16:35Partial coverage0 min—
Mon 19 OctEnschede Kennispark 16:10Partial coverage0 min—
Sun 18 OctEnschede Kennispark 16:08+2 min+2 min
Sat 17 OctEnschede Kennispark 16:05No data—
Fri 16 OctEnschede Kennispark 16:05No data—
Thu 15 OctEnschede Kennispark 16:06No data—
Wed 14 OctNijverdal 15:33No data—
Tue 13 OctEnschede Kennispark 16:06No data—
Mon 12 OctEnschede Kennispark 16:06Partial coverage0 min—
Sun 11 OctEnschede Kennispark 16:06Partial coverage+1 min—
Sat 10 OctEnschede Kennispark 16:06Partial coverage0 min+1 min
Fri 9 OctEnschede Kennispark 16:06Partial coverage+1 min—
Thu 8 OctEnschede Kennispark 16:07Partial coverage+2 min+2 min
Wed 7 OctEnschede Kennispark 16:05No data—