Thin sample this season. Noussair Mazraoui has played 4 matches (160 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
in the first line of build-up — mostly in the middle third (50% of his 121 passes)
88% completion · 121× in 4/4 matches
↓
CARRY OUT
step into midfield to commit a presser
3 carries · 6× in 3/4 matches
↓
BREAK A LINE
vertical pass past the opponent midfield
2.8 prog/90 · 7× in 2/4 matches
↓
PROGRESS
entries into the final third
5.6/90 · 10× in 2/4 matches
Signature: Receive → Carry Out → Break A Line → Progress — the only steps proven repeatable this season (4 of 5 in the full pattern). Not enough evidence yet for the rest of the chain below.
Not a pattern: switch play — 1× (low confidence, shown as a number only, no tactical conclusion drawn) — omitted from the signature rather than presented as one.
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 →
30
passes / match
15.2
def actions / 90
3–83
pass range (matches)
9
clearances
Pass range = his fewest and most passes in any single match this season (3 at the low end, 83 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.
26 tracked carries (14.6/90, 7 progressive, 230m 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 26 carries originating in each zone · own goal left, attacking →
Every carry, exact path — median 6m, longest 38m
By zone — where the carry started → where it ended
First (19)Second (7)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
1
won
2
beaten · 67%
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 2 of 3 tackle duels (67% loss rate) — a solid 1v1 defensive record.
Every tackle duel, exact location
wonlost — dribbled pastown goal left, attacking →
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.
08
How does he create chances?
3 key passes (1.69/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 (3)assist (0)% of the selected group's key passes originating in each zone
03
Where does he become vulnerable?
18 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)
6
middle third
4
own third (dangerous)
Vision AI 44% of losses are in the attacking third — a notable share happen deeper, which invites transitions.
Mistake danger (proxy): 3.35 danger-index/90 · 0.330 avg/turnover. Weights each loss by threat conceded at that location. True xT-conceded needs the opponent possession model; positional proxy.
04
Where Does He Receive?
The zones where Noussair Mazraoui 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
20%
Primary
Right Wing, Attacking third
16%
Secondary
Right Wing, Middle third
15%
Third
Right Half-Space, Middle third
These are the zones where he collected the ball most.
05
Where Does He Operate? — Every Zone
Every on-ball touch (pass, dribble, shot) binned into a 6×3 grid — raw counts of where Noussair Mazraoui 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 →
07
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 3 key passes, his busiest route is a delivery where he plays inside from the right wing toward 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 wing in the final third: 20% of his 25 touches there are lost (5 times).
27 defensive actions across the season (15.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 →
3
tackles · 33% won
1
interceptions · 0.6/90
5
recoveries · 2.8/90
9
clearances · 5.1/90
1
blocks
27
avg action height
1
won high (att 3rd)
9
middle third
17
own third
Vision AI A deep-defending defender. He wins the ball mainly by clearing and blocking — a reactive, protect-the-box profile. 9 proactive ball-wins (5.1/90), tackle success 33%. He defends deep, protecting his box — a last-line stopper.
Team
Team context
How much of the team runs through him, and what changes without him.
Man Utd's output per match with Noussair Mazraoui (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. 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 (4)
WITHOUT (4)
Δ
goals against /match
1.75
1.50
+0.25
points /match
1.25
0.50
+0.75
goals for /match
2.00
0.50
+1.50
xG for /match
1.99
1.03
+0.96
11
His Share of the Team
Of everything Man Utd produced this season, the categories where the biggest share ran through Noussair Mazraoui specifically — his share of the team total, not a per-90 rate.
category
share
him / team
clearances
6%
70 / 1159
tackles
4%
31 / 820
final-third entries
4%
82 / 2305
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 513 centre-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.
Stopper centre-back66%Ball-playing centre-back56%
Why Stopper centre-back 66%: a weighted blend of ball-winning 80 (weight 40%) + defensive aggression 46 (weight 35%) + retention 48 (weight 15%) + transition 57 (weight 10%). The score reflects how distinctively his profile SHAPE matches this archetype vs his peers.
Elite
receiving zones, line-breaking, territory (wide vs central), progression, crossing
aerial ability, marking, off-ball running — not in event data
Receiving zones
97
Line-breaking
95
Territory (wide vs central)
91
Progression
87
Crossing
86
Final-third threat
83
Through-balls ~proxy
81
Ball-winning
80
Creativity
77
Carrying
69
Dribbling
65
Transition ~proxy
57
Retention
48
Press resistance ~proxy
47
Defensive aggression
46
Build-up
42
Box threat
38
Passing directness
21
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: 183 cm / 79 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.
Jonny Alaves · La Liga · 175 cm / 70 kg
89%
Driven by: territory (wide vs central) (11%), crossing (11%), ball-winning (9%). Different mechanism — Mazraoui more via receiving zones.
Malo Gusto Chelsea · 178 cm / 67 kg
89%
Driven by: receiving zones (15%), creativity (13%), ball-winning (10%). Different mechanism — Mazraoui more via passing directness, carrying; Gusto more via defensive aggression, creativity.
Nahuel Molina Roma · Serie A · 175 cm / 70 kg
88%
Driven by: receiving zones (14%), creativity (13%), progression (10%). Different mechanism — Mazraoui more via retention; Molina more via box threat, defensive aggression.
Olivier Boscagli Brighton · 181 cm / 68 kg
87%
Driven by: progression (13%), receiving zones (13%), final-third threat (12%). Different mechanism — Mazraoui more via territory (wide vs central); Boscagli more via defensive aggression, passing directness.
Tino Livramento Newcastle · 183 cm / 71 kg
87%
Driven by: receiving zones (14%), crossing (13%), line-breaking (12%). Different mechanism — Mazraoui more via ball-winning, carrying.
Victor Chust Elche · La Liga · 182 cm / 77 kg
86%
Driven by: receiving zones (16%), progression (13%), final-third threat (12%). Different mechanism — Mazraoui more via territory (wide vs central).
15
Summary
Noussair Mazraoui is a stopper centre-back / ball-playing centre-back: 88% pass completion, 7 line-breaking passes and 2.8 progressive passes /90. A build-and-progress centre-back whose value is in beating the first line with the pass, not in raw defensive volume. [Aerial duels, marking, line-height and 1v1 recovery need aerial-event + tracking data, absent here.]
Based on 4 matches (160 minutes) — an early read, treat with caution until more minutes are logged. He profiles as a stopper centre-back / ball-playing centre-back — best used in a system built around that identity.
His biggest room for growth is defensive aggression — even a modest improvement there would meaningfully lift his overall stopper centre-back 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.