Ligue 1 · France
confirmed lineupToulouseToulouse last 1, most recent first: lost 0-2 at home to Lyon. v LyonLyon last 1, most recent first: won 2-0 away at Toulouse.
Best edge
—
no call published
Angles
—
none found
Referee
-52%
Guillaume Paradis · cards v league
No value call published on this fixture
No edges published on this fixture. An edge is published only when a bookmaker's price beats the model's fair price by that market's full bar — most fixtures never produce one. The value board explains every gate a candidate has to clear.
- Fouls/game
- 21.0-9%
- Cards/game
- 2.0-52%
- Minutes
- 0 confirmed
- 0 expected
- 0 provisional
The XI is out, so the only thing left to model is when each of them comes off.
Value — 0 live calls
Published at the price shown, scored against the closing line.
No edges published on this fixture. An edge is published only when a bookmaker's price beats the model's fair price by that market's full bar — most fixtures never produce one. The value board explains every gate a candidate has to clear.
The confirmed XI. This capture carries no shape, so players are placed by their own registered position in four bands — the weaker claim of the two.
Recent results
Last six completed matches per side, newest first. Half-time score in brackets where the feed carries one.
- 22 AugHLyon0-2L
- 22 AugAToulouse2-0W
Player props
Model projections. Nothing here has been compared to a bookmaker.
How this is calculated →No projections for this fixture yet. The projection job runs against fixtures inside the odds window, and only for players with at least 10 completed matches on record.
Trends and angles
Form against the lines the books are pricing, what the opposition concede, and the referee against his league.
No angles on this fixture. An angle needs priced lines in the feed and a run long enough to be worth stating — most fixtures produce some once the books put player props up.
Referee
§5.1: the dominant covariate for fouls, and the reason two identical players price differently on different days.
Guillaume Paradis
1 matches on record
Fouls per game
21.0
-9% vs leagueleague 23.2 fouls
Cards per game
2.0
-52% vs leagueleague 4.1 cards
Cards, home side
1.0
Toulouse
Cards, away side
1.0
Lyon
Fouls — every foul committed by both teams in a match he refereed, averaged over his completed matches. The match being previewed is never in it. Under 15 matches on record, so the model itself falls back toward the league mean here.
Cards — any card, yellow or red, both teams. The same definition the card props settle against, so this figure and the Cards market count the same events. A dismissal that the feed records as a second yellow counts as two.
Both league averages are the mean across all five competitions Per90 covers, not this fixture's league alone — the fouls comparison has always been that, and the cards comparison is built the same way so the two percentages beside each other mean the same thing.
The model
What the numbers on this page are, and what they are not.
How are these projections calculated?OpenClose
Not tips and not prices. Each row is the model's expected count for one player in this match — how many fouls, tackles or shots it thinks he records — plus the full spread of outcomes around it. Nothing in the projections has been compared to a bookmaker; that comparison is what the Value tab is.
Step 1
His own record
Every completed match in the dataset, as a rate per 90 minutes. The n column is how many matches that rests on.
Step 2
Pulled toward his position
A thin record gets pulled hard toward other players in his position, in his league — a goalkeeper toward goalkeepers, not toward the outfielders around him. How hard is fitted per market, not chosen: tackles pull about four times harder than shots on target.
Step 3
This fixture's conditions
How much of the stat the opponent concedes, what the referee’s matches look like, and home or away. This is where a projection stops being a season average.
Step 4
Scaled to expected minutes
A rate becomes a count only once you say how long he plays. 60 minutes carries two-thirds the exposure of 90, and the distribution is built at that exposure.
How to read each column
- Model /90
- The model’s rate for this match with the minutes taken back out — steps 1 to 3 already applied. It moves with the opponent and the referee, so it is not his raw career rate; the builder shows career and model rates side by side. Open any row to see it.
- Exp. mins
- Minutes the model expects. Confirmed means the lineup is out; provisional means it is guessing from his start rate, and is the widest of the three.
- Projected
- The expected count in this match, at those minutes. This is the number a line is set against.
- Over 1.5, etc.
- Read straight off the distribution beside it, not off how often he has beaten that line before. It answers what the model thinks, not what has happened.
- n
- Matches behind his own rate. Under 30 it turns amber: the projection is mostly his position group speaking, and §6.3 will not publish an edge on it.
- Distribution
- The whole spread, not just the average. The dashed amber cut is the line; jade bars beat it. An expected 1.8 fouls made of 2 every week and an expected 1.8 made of a 0 and a 5 are different bets, and this is where you see which one you have.
Counts are modelled as negative binomial rather than Poisson, because fouls and tackles are overdispersed and a Poisson would systematically underprice the tails — which is exactly where over bets live. Every market on this page cleared its calibration gate before it was allowed to produce a projection: when the model says 60%, it lands within a point or so of 60% out of sample.
The full write-up — every gate, every fitted parameter and what the model refuses to price — is on the methodology page.