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
Left Wing, Middle third — mostly in the middle third (43% of his 106 passes)
50% completion · 106× in 4/4 matches
↓
PROGRESS
drive or pass into the final third
6.1 prog/90 · 11× in 2/4 matches
Signature: Receive → Progress — the only steps proven repeatable this season (2 of 4 in the full pattern). Not enough evidence yet for the rest of the chain below.
Not a pattern: arrive — 2× (low confidence, shown as a number only, no tactical conclusion drawn); create / finish — 1× (insufficient confidence, hidden — not enough evidence yet) — omitted from the signature rather than presented as one.
13
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 →
26
passes / match
1.5
dribbles / match
4–60
pass range (matches)
1–2
dribble range (matches)
Pass range = his fewest and most passes in any single match this season (4 at the low end, 60 at the high) — a measure of match-to-match involvement, not pass distance. Dribble range works the same way, for dribbles/carries per match.
In possession
In possession
What he does with the ball: build-up, progression, creation, carrying and finishing.
13 tracked carries (7.2/90, 1 progressive, 111m total) — the ball moving with his touches, a different signal from dribbles below (beating an opponent 1v1). this counts every touch-carry, not just his dribble attempts below — a fuller picture of how much of his ball-carrying is control-and-move rather than beating a man.
progressivelateral/short% of his 13 carries originating in each zone · own goal left, attacking →
Every carry, exact path — median 8m, longest 22m
By zone — where the carry started → where it ended
First (13)grouped by carry pattern (start + end position), largest group first
startendown goal left, attacking →
Dribbles (1v1s)
Only 3 dribbles attempted this season — too little volume to map a location pattern.
02
How does he create chances?
0 key passes (0.00/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 (0)assist (0)% of the selected group's key passes originating in each zone
04
Where does he become vulnerable?
56 possessions lost. Directness has a cost — the question is where. Attacking-third losses are cheap; deep ones are dangerous.
19
attacking third (cheap)
22
middle third
15
own third (dangerous)
Vision AI 34% of losses are in the attacking third — a notable share happen deeper, which invites transitions.
Mistake danger (proxy): 10.94 danger-index/90 · 0.352 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 David Puczka 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
36%
Primary
Left Wing, Middle third
28%
Secondary
Left Wing, Attacking third
21%
Third
Left Wing, Defensive 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 David Puczka 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 →
09
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 →
How does he progress the ball forward?
His most common route for progressing play: he plays inside from the right wing toward the left hs, advancing it forward in the middle third — 1 passes worth 0.37 xT.
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 left wing in the final third: 59% of his 29 touches there are lost (17 times).
08
Crosses & Cutbacks
9 crosses (5.00/90, 2 completed) and 1 cutbacks (0.56/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.
Crosses — close-up on the final third
Cutbacks — close-up on the final third
completedfailed (dashed)close-up on the box — attacking ↑ toward goal
31 defensive actions across the season (17.2/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 →
8
tackles · 50% won
0
interceptions · 0.0/90
6
recoveries · 3.3/90
5
clearances · 2.8/90
3
blocks
33
avg action height
3
won high (att 3rd)
10
middle third
18
own third
Vision AI A deep-defending defender. He wins the ball mainly by stepping in — tackles, interceptions & recoveries outweigh clearances. 14 proactive ball-wins (7.8/90), tackle success 50%. He defends mostly around the middle third.
Team
Team context
How much of the team runs through him, and what changes without him.
Genoa's output per match with David Puczka (4 matches) versus without him (4 matches). Insufficient evidence — the without-sample is only 4 matches; treat every Δ below as noise until more games exist. A proper on-off model needs many more minutes.
WITH (4)
WITHOUT (4)
Δ
goals for /match
1.00
0.50
+0.50
xG for /match
0.61
1.05
-0.44
goals against /match
1.25
2.00
-0.75
points /match
1.50
0.25
+1.25
12
His Share of the Team
Of everything Genoa produced this season, the categories where the biggest share ran through David Puczka specifically — his share of the team total, not a per-90 rate.
category
share
him / team
tackles
1%
8 / 749
progressive passes
1%
16 / 1684
final-third entries
1%
12 / 1394
Recruitment
Style and verdict
Style profile, closest comparables, and the summary.
David Puczka is a central mid: 6.1 progressive passes, 0.00 key passes /90, 2 box entries, 0 goals from 0.02 xG. A box-to-box contributor across every phase.
Based on 4 matches (162 minutes) — an early read, treat with caution until more minutes are logged. He profiles as a central mid — best used in a system built around that identity.
✨ 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.
