العربيةSeason
← BACK TO SEARCH
Building the full report
Combining every season — this one is larger, give it a moment.
← BACK TO SEARCH
← BACK TO SEARCH
Who he is and how he compares with his peers.
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.
What he does with the ball: build-up, progression, creation, carrying and finishing.
34 tracked carries (8.2/90, 7 progressive, 318m 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 3 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.
How he moves the ball — his 4 busiest progression routes, not where every pass starts and ends separately. Arrow width = how often, colour = xT gained, dashed = switch of play. The full breakdown is in the lane matrix below.
Primary route: the right wing in the final third → the right wing in the final third — 6 progressive passes (21% of his progression) at 0.043 xT each. He keeps it in the same lane.
His progression is inward: 61% of progressive passes move the ball toward the middle versus 0% going wider — he cuts in rather than holding width.
Only 7% of his passes switch play, so his threat is same-side — contain the flank he occupies and the route closes.
Quality behind the volume: 7 line-breaking passes and 8 final-third entries, 3.2 total xT added.
2 key passes (0.48/90), 0 of them assists — where his chance creation specifically comes from, 18 zones (6×3), showing his share of key passes originating there.
29 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 Kiko Femenía 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 Kiko Femenía 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.
Same zone grid, restricted to passes so completed/incomplete and match filters actually mean something — a shot or a dribble has no "completed" in the pass sense.
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.
Where and how he defends and presses.
43 defensive actions across the season (10.4/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 Kiko Femenía 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.
How much of the team runs through him, and what changes without him.
Getafe's output per match with Kiko Femenía (6 matches) versus without him (4 matches). Insufficient evidence — the without-sample is only 4 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 Getafe produced this season, the categories where the biggest share ran through Kiko Femenía specifically — his share of the team total, not a per-90 rate.
Style profile, closest comparables, and the summary.
Not raw event counts — football style scores: weighted models scored 0–100 against the 233 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: 176 cm / 61 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 La Liga, Bundesliga, Ligue 1, Premier League 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.
Kiko Femenía is an overlapping full-back: 2.4 progressive passes and 1 box entries, delivering 2 key passes. Overlap-first full-back. [1v1 recovery pace and off-ball overlap timing need tracking.]
Click any stat card to filter its map, hover a dot for the exact match, and use the dropdowns to slice passes zone-to-zone. Nothing here is static.