This page describes the completed match context. The result is not presented as a prior forecast.
This match
Match statistics
| Metric | Sheffield Wednesday | Coventry City |
|---|---|---|
| Shots | 9 shots/match | 21 shots/match▲ |
| Shots on target | 0 shots/match | 10 shots/match▲ |
| Expected goals | 1.05 xG/match | 4.94 xG/match▲ |
| Possession | 52% | 48% |
| Corners | 13 corners/match | 8 corners/match |
| Fouls | 9 fouls/match | 3 fouls/match |
Every shot
Shot map
Every recorded shot, placed where it was taken and sized by its expected-goals value. Each team attacks towards its own end of the pitch.
- off target
- on target
- goal
- penalty
- size = xG
Sheffield Wednesday: 9 shots, 0 on target, 1.10 xG. Coventry City: 21 shots, 10 on target, 4.97 xG.
How the match built
Expected-goals timeline
Expected goals accumulated minute by minute. Circles mark the goals that were actually scored.
The step line is cumulative expected goals; circles mark goals. Final: Sheffield Wednesday 1.10 xG · Coventry City 4.97 xG.
30-second read
What the record shows
The clearest recorded pattern is: Coventry City's shot volume and the opposing shot-allowance context sit above their competition baselines. A second useful context is: A compressed recent schedule is recorded for Sheffield Wednesday, Coventry City. Limitation: Evidence is usable but does not meet the strongest completeness threshold.
Coventry City show a distinct attacking-volume record
moderateCoventry City's shot volume and the opposing shot-allowance context sit above their competition baselines.
Evidence and caveat
Comparison: Team shot volume is paired with the opponent's recorded shot allowance.
Window: season
| Metric | Sheffield Wednesday | Coventry City | Baseline |
|---|---|---|---|
| Shots | 11 shots/match | 17.7 shots/match | 12.4 shots/match |
| Shots against | 17.3 shots/match | 10.2 shots/match | 12.4 shots/match |
Caveat: Shot volume describes activity; it does not establish finishing quality or a match outcome.
Recent scheduling adds useful context
moderateA compressed recent schedule is recorded for Sheffield Wednesday, Coventry City.
Evidence and caveat
Comparison: Rest days and completed matches in the prior 14 days are shown directly.
Window: previous 14 days
| Metric | Sheffield Wednesday | Coventry City | Baseline |
|---|---|---|---|
| Rest days | 3.7 days | 2.7 days | — |
| Matches last 14 days | 3 matches | 3 matches | — |
Caveat: The database does not describe travel, rotation decisions or player-level workload.
Both teams have elevated corners records
moderateEach team's season corners average is above the competition baseline.
Evidence and caveat
Comparison: Both team averages are compared with the same competition baseline.
Window: season
| Metric | Sheffield Wednesday | Coventry City | Baseline |
|---|---|---|---|
| Corners | 5.67 corners/match | 6.11 corners/match | 4.8 corners/match |
Caveat: A shared historical pattern is descriptive and may not repeat in one fixture.
Metric comparison
Values, percentiles and samples
Sheffield Wednesday favored in 0 of 14 directional metrics · Coventry City in 11 · 3 too close
Style profile
How the teams compare
Competition percentiles describe recorded style; they do not rank likely outcomes.
Possession control
Relative share of recorded possession within the competition.
Attacking volume
Recorded shot and scoring volume, expressed as competition percentiles.
Defensive resistance
Lower recorded scoring and shot allowance produces a higher descriptive percentile.
Directness proxy
Shots per possession point; a descriptive transition/directness proxy, not an outcome score.
Physicality
Recorded fouls and cards relative to competition peers.
Set-piece relevance
Corner volume relative to competition peers.
Tempo and pressure proxy
Combined event-volume percentiles for shots, corners and fouls.
Recent form
Season, last 10 and last 5
Window
Last 5
Window
Last 10
Window
Season
Venue split
Home and away samples
Window
Home team at home / away team away
Schedule context
Rest and recent workload
Evidence quality
How much supports this analysis
- Evidence is usable but does not meet the strongest completeness threshold.
Known unknowns
- Lineups, injuries, suspensions and tactical changes are not available in the retained dataset.
- Some metrics are unavailable or below their observation minimum: cards.
Make a graphic from this match
Creator Studio builds a branded post from this match's recorded data, with its evidence grade and source cutoff carried into the export.