GRABBLESTATS
Watch🏴󠁧󠁢󠁥󠁮󠁧󠁿 Premier League · · 13:00
versus

Leeds
Brentford

Elland Road
Pre-match analysis
59%
Both teams to score
LE36
Draw27
BR37
Compared profiles
57Attack63
50Transition78
67Defence45
50Set pieces43
50Possession28
48Game Control48
Action zones · density map
0Finishing0Chance Creation50Set Pieces
50Transition
0Defensive Line0Aerial
0100absolute scale, not stretched to this fixture

Peak for Leeds: set pieces in the attacking third, at 50.

The map comes from the fixture's axes, not from positional tracking: it says where play concentrates, never where a player stood. There is no left/right split because the product holds no flank data — inventing three identical columns would be an image pretending to measure what it does not.

Factors taken into accountcontribution in points

No signal is measured for this fixture. A signal is a weighted factor carrying its contribution in points; until the ingested history supports one, the analysis stands on the probability alone.

LEELEE
BREBRE
Elland Road · Pre-match analysis
59%
Both teams to score

Advantage by third

derived from the match-up axes — not tracking data
LEEfaibleélevé
5050
Middle third
Transition
Attacking third
Set Pieces
BREfaibleélevé
7843
Middle third
Transition
Attacking third
Set Pieces

Each third is scored from the axes that describe it, home minus away. There is no left/right split because the product holds no flank data — it is not invented to fill the picture.

LE BR
LEBR

Home record vs away record

i
LEE · at homeBRE · away
1.84Points per game1.28
13–7–5W–D–L9–5–11
0.00Goals for / match0.00
0.00Goals against / match0.00

Over 25 home and 25 away fixtures this season.

Team DNA comparison

i
LEELEEUnmeasured
Attack
57
Transition
50
Defence
67
Set Pieces
50
Possession
50
Game Control
48
BREBREStrong
Attack
63
Transition
78
Defence
45
Set Pieces
43
Possession
28
Game Control
48

Statistics

i
LEE LEEBRE BRE
73Goals scored (season)73
65Goals conceded (season)66
8GD7

Similar matches(past meetings, as the registry holds them)

All comparable situations

i
SimilarityFixtureDateResultWhy similar