Aaron Wan-Bissaka

His repeatable signature. A step only appears if its reliability score (sample size × match coverage) reaches at least Medium confidence — pattern mining, not anecdotes.

Red fill = raw touch territory. Gold rings = zones where his influence (xT added, progression, line-breaks, key passes) outweighs how often he's actually there — one combined map instead of two separate maps to compare by eye. Red with no ring: present but not dangerous. A ring on faint red: rare touches, outsized impact.

29 tracked carries (8.7/90, 9 progressive, 297m total) — the ball moving with his touches, a different signal from dribbles below (beating an opponent 1v1). even a player who rarely dribbles past a man can still carry the ball forward constantly in build-up; this is that.

How often an attacker gets past him in a 1v1 defensive duel — the closest signal the data has to "dribbled past" (no attacker-beat-defender field exists directly, so this counts tackles he attempted and lost).

He attempted only 5 dribbles of his own all season — dribbling is not part of this role; his ball-carrying is covered above, his defending against the dribble below.

2 key passes (0.60/90), 0 of them assists — where his chance creation specifically comes from, 18 zones (6×3), showing his share of key passes originating there.

27 times he gave the ball away. For a defender the danger is where — a loss in his own third can turn into a chance against; higher up it costs little.

The zones where Aaron Wan-Bissaka gets on the ball — his top three ball-collection areas highlighted (gold = primary). Reception is proxied by where his on-ball actions begin (no explicit receiver is recorded).

Every on-ball touch (pass, dribble, shot) binned into a 6×3 grid — raw counts of where Aaron Wan-Bissaka actually gets on the ball. Hover any zone for its breakdown by action type, its share of all touches, and the exact coordinate range it covers.

Every pass this season, plotted individually — green = completed, grey (dashed) = incomplete, gold = key pass. Filter by outcome or isolate one match below.

Three clustered sequence diagrams from his own event data — his three busiest routes: the way he progresses, the pattern behind his chances, and where a turnover turns dangerous.

4 crosses (1.20/90, 1 completed) and 2 cutbacks (0.60/90, 0 completed) — two separate wide-delivery patterns into the box, each its own map with a completed/failed filter. Neither is a tagged event, so both are inferred from pass geometry — the intended end point of a failed attempt is still real data (an interception doesn’t erase where the ball was aimed): a cross is a pass aimed into the box starting from a wide channel; a cutback starts almost on the byline but is squared back rather than driven forward, aimed centrally around the box. The completed-cross count was checked against this platform’s own real match-level cross totals and lands within about 1 cross of the true count.

46 defensive actions across the season (13.8/90). Where he wins the ball, and how — the core question for a defender. Aerial duels are not recorded for this competition, so aerial dominance is not measured here.

Split by how hard the opponent pressed (opponent PPDA — lower = more intense press). Can Aaron Wan-Bissaka still play out when the opponent presses high? His build-up quality split by press intensity — the key question for a ball-playing defender. Tiers of ~2-2 matches — directional evidence, not proof.

Aston Villa's output per match with Aaron Wan-Bissaka (6 matches) versus without him (2 matches). Insufficient evidence — the without-sample is only 2 matches; treat every Δ below as noise until more games exist. What his own defending should move — goals conceded and results — leads; attacking output (largely out of a defender's hands) is shown after, for context. A proper on-off model needs many more minutes.

Of everything Aston Villa produced this season, the categories where the biggest share ran through Aaron Wan-Bissaka specifically — his share of the team total, not a per-90 rate.

Not raw event counts — football style scores: weighted models scored 0–100 against the 232 full-backs in the pool (min 450 min). This is what separates players who post similar numbers but play differently. Proxy dimensions are inferred from on-ball data; true off-ball running / under-pressure context is not measured.

Closest comparables measured on the style scores above, within the same position family — so it separates how players are alike, not just how much they touch the ball. Each line explains the shared strength and the divergent mechanism. A light physical-profile term (height / weight; this player: 183 cm / 72 kg) is included at a quarter of one style axis's weight — enough to break ties between stylistic twins, not to override style. Scope: pooled across the Premier League, Bundesliga, La Liga, Ligue 1 and Serie A, percentiled within each player's own league before comparing — a match from another league is marked with its league name.

Style, not quality: a high match here means two players tend to produce the ball in similar ways — it is not a ranking, a scouting recommendation, or a claim that they are equally good.

Aaron Wan-Bissaka is an overlapping full-back: 3.9 progressive passes and 2 box entries, delivering 2 key passes. Overlap-first full-back. [1v1 recovery pace and off-ball overlap timing need tracking.]