Thin sample this season. Frank Anguissa has played 5 matches (342 min) so far, so sections that need a bigger sample to say anything reliable are not shown here — they are missing on purpose, not broken. See all seasons combined →
01
What Patterns Define Him?
His repeatable signature. A step only appears if its reliability score (sample size × match coverage) reaches at least Medium confidence — pattern mining, not anecdotes.
RECEIVE
drop between the centre-backs — mostly in the middle third (57% of his 133 passes)
86% completion · 133× in 5/5 matches
↓
ESCAPE PRESSURE
turn out of a tight central area
40% won · 5× in 3/5 matches
↓
PROGRESS CENTRAL
break a line through the middle
1.6 prog/90 · 4× in 3/5 matches
↓
SCREEN / WIN BALL
protect the back four
6.3 ball-wins/90 · 24× in 5/5 matches
↓
RECYCLE / PROGRESS
keep it ticking, feed the final third
2.4 f3-entries/90 · 9× in 4/5 matches
Signature: drop to receive → escape the press on the turn → progress centrally or recycle → screen the counter. Block the central lane and press his first touch to force him backwards.
12
Where is he influential — vs where is he merely present?
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.
own goal left, attacking →
27
passes / match
12.9
def actions / 90
4–47
pass range (matches)
5
clearances
Pass range = his fewest and most passes in any single match this season (4 at the low end, 47 at the high) — a measure of match-to-match involvement, not pass distance.
In possession
In possession
What he does with the ball: build-up, progression, creation, carrying and finishing.
25 tracked carries (6.6/90, 3 progressive, 195m 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.
progressivelateral/short% of his 25 carries originating in each zone · own goal left, attacking →
Every carry, exact path — median 7m, longest 28m
By zone — where the carry started → where it ended
First (15)Second (10)grouped by carry pattern (start + end position), largest group first
startendown goal left, attacking →
Beaten in the tackle
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).
3
tackle duels
2
won
1
beaten · 33%
brighter band = more tackle duels · own goal left, attacking →
INSIDE 67%
OUTSIDE 33%
Tackle-duel location — 2 inside · 1 outside
Right Wing
1 · 33%
Right Half-Space
0 · 0%
Central
2 · 67%
Left Half-Space
0 · 0%
Left Wing
0 · 0%
Vision AI beaten in 1 of 3 tackle duels (33% loss rate) — a solid 1v1 defensive record.
Every tackle duel, exact location
wonlost — dribbled pastown goal left, attacking →
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.
04
How does he create chances?
2 key passes (0.53/90), 0 of them assists — where his chance creation specifically comes from, 18 zones (6×3), showing his share of key passes originating there.
Chance creation — key pass origin zone share
Filter:
chance creation (2)assist (0)% of the selected group's key passes originating in each zone
03
Where does he become vulnerable?
22 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.
8
attacking third (cheap)
10
middle third
4
own third (dangerous)
Vision AI 36% of losses are in the attacking third — a notable share happen deeper, which invites transitions.
Mistake danger (proxy): 1.89 danger-index/90 · 0.327 avg/turnover. Weights each loss by threat conceded at that location. True xT-conceded needs the opponent possession model; positional proxy.
05
Where Does He Receive?
The zones where Frank Anguissa 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).
1 = primary, 2 = secondary, 3 = third · own goal left, attacking →
His collection zones
19%
Primary
Right Half-Space, Middle third
17%
Secondary
Central, Middle third
10%
Third
Right Wing, Middle third
These are the zones where he collected the ball most.
06
Where Does He Operate? — Every Zone
Every on-ball touch (pass, dribble, shot) binned into a 6×3 grid — raw counts of where Frank Anguissa 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.
Filter:
own goal left, attacking → · brighter + higher number = more touches
Passes only — completed vs incomplete, by zone
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.
own goal left, attacking →
08
Every Pass This Season — completed vs incomplete
Every pass this season, plotted individually — green = completed, grey (dashed) = incomplete, gold = key pass. Filter by outcome or isolate one match below.
Tactical patterns — how his football actually looks
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.
own goal left, attacking →
Where do his chances come from?
Of 2 key passes, his busiest route is a delivery where he switches it out from the central to the right hs, advancing it forward in the middle third — 1 times. The receiver isn't identifiable in this data, only where the pass started and ended.
Where does he lose the ball most?
This is a RATE, not a raw count — the share of his touches in each zone that end in a turnover, so a zone he simply plays in more often doesn't automatically look riskier. His weakest zone is the right half-space in the final third: 62% of his 8 touches there are lost (5 times).
49 defensive actions across the season (12.9/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.
click a card to isolate that action type · own goal left, attacking →
3
tackles · 67% won
3
interceptions · 0.8/90
18
recoveries · 4.7/90
5
clearances · 1.3/90
3
blocks
42
avg action height
8
won high (att 3rd)
20
middle third
21
own third
Vision AI A mid-block defender. He wins the ball mainly by stepping in — tackles, interceptions & recoveries outweigh clearances. 24 proactive ball-wins (6.3/90), tackle success 67%. He defends high, stepping out to intercept — suits a high line.
Team
Team context
How much of the team runs through him, and what changes without him.
Napoli's output per match with Frank Anguissa (5 matches) versus without him (3 matches). Insufficient evidence — the without-sample is only 3 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.
WITH (5)
WITHOUT (3)
Δ
goals against /match
1.80
0.33
+1.47
points /match
1.00
2.00
-1.00
goals for /match
1.80
1.33
+0.47
xG for /match
1.56
0.88
+0.68
11
His Share of the Team
Of everything Napoli produced this season, the categories where the biggest share ran through Frank Anguissa specifically — his share of the team total, not a per-90 rate.
category
share
him / team
goals
11%
1 / 9
interceptions
6%
15 / 247
expected goals (xG)
5%
3.6 / 66.0
Recruitment
Style and verdict
Style profile, closest comparables, and the summary.
Not raw event counts — football style scores: weighted models scored 0–100 against the 258 defensive mids 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.
Tempo controller63%Deep-lying playmaker57%Ball-winning 641%
Why Tempo controller 63%: a weighted blend of retention 64 (weight 35%) + build-up 66 (weight 30%) + press resistance 66 (weight 20%) + progression 28 (weight 15%). The score reflects how distinctively his profile SHAPE matches this archetype vs his peers.
line-breaking, passing directness, territory (wide vs central), ball-winning, progression
Unknown
aerial ability, marking, off-ball running — not in event data
Box threat
91
Receiving zones
74
Dribbling
69
Build-up
66
Press resistance ~proxy
66
Retention
64
Defensive aggression
60
Creativity
56
Through-balls ~proxy
49
Transition ~proxy
49
Carrying
48
Crossing
46
Final-third threat
40
Line-breaking
38
Passing directness
36
Territory (wide vs central)
34
Ball-winning
34
Progression
28
14
Similar Players — in style space
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: 184 cm / 78 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 Serie A, Bundesliga, La Liga, Ligue 1 and Premier League, 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.
Jens Stage Werder Bremen · Bundesliga 25/26 · 187 cm / 81 kg
68%
Driven by: box threat (44%), ball-winning (19%), receiving zones (9%). Different mechanism — Anguissa more via through-balls, retention; Stage more via passing directness.
Thomas Partey Villarreal · La Liga 25/26 · 185 cm / 77 kg
64%
Driven by: box threat (19%), receiving zones (17%), dribbling (15%). Different mechanism — Anguissa more via territory (wide vs central), box threat; Partey more via carrying, dribbling.
Marc Bernal Barcelona · La Liga · 193 cm / 87 kg
61%
Driven by: box threat (17%), press resistance (15%), receiving zones (15%). Different mechanism — Anguissa more via territory (wide vs central), passing directness; Bernal more via creativity, ball-winning.
Roméo Lavia Chelsea · Premier League · 181 cm / 76 kg
56%
Driven by: box threat (15%), territory (wide vs central) (14%), press resistance (13%). Different mechanism — Anguissa more via through-balls, territory (wide vs central); Lavia more via passing directness, retention.
Michaël Cuisance Lens · Ligue 1 · 181 cm / 74 kg
54%
Driven by: box threat (32%), passing directness (12%), defensive aggression (10%). Different mechanism — Anguissa more via receiving zones, passing directness; Cuisance more via ball-winning, carrying.
Leon Goretzka Aston Villa · Premier League · 189 cm / 82 kg
52%
Driven by: box threat (28%), receiving zones (16%), press resistance (13%). Different mechanism — Goretzka more via progression, final-third threat.
15
Summary
Frank Anguissa is a tempo controller / deep-lying playmaker: 86% completion, 4 line-breaks and 1.6 progressive passes /90, resisting pressure with 40% dribble success. A central controller. [Off-ball screening position and scanning need tracking data.]
Based on 5 matches (342 minutes) — an early read, treat with caution until more minutes are logged. He profiles as a tempo controller / deep-lying playmaker — best used in a system built around that identity.
His biggest room for growth is progression — even a modest improvement there would meaningfully lift his overall tempo controller profile.
✨ This report is interactive
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.