Loading the page
Both teams to score · Thursday, October 15
Both teams to score predictions today
The day's fixtures that the engine rates more likely than not to see both sides score, most likely first. Each price is a bookmaker's where one was quoted, and the engine's own fair price where not.
Last 30 days, every settled call
56.2%194 of 345 landed, against 52.6% of all matches on record
Live, stored before kick-off
56.6%159 of 281
Reconstructed after the match
54.7%35 of 64
BTTS is only counted as a pick where the engine rates yes above 50%. A fixture it rates under is not a pick that failed to land. Read the rate against how often both teams score anyway, quoted above: beating that is the claim, not the raw percentage.
Today's both teams to score picks
15 of 15 fixtures on this card had a view for this market. Prices marked ≈ are the engine’s own fair price, not a bookmaker’s.
Latest settled BTTS winners
- DC United 2–1 New York Red Bullscalled Both teams to score at 56.0%live
- Toronto FC 3–3 Orlando Citycalled Both teams to score at 62.7%live
- FC Cincinnati 2–3 New England Revolutioncalled Both teams to score at 64.5%live
- Columbus Crew 3–1 Charlottecalled Both teams to score at 57.5%live
- Queens Park Rangers 4–1 Derbycalled Both teams to score at 50.5%live
- Portsmouth 3–2 Sheffield Unitedcalled Both teams to score at 51.5%live
- Stoke 2–3 Middlesbroughcalled Both teams to score at 50.7%live
- Wrexham 1–2 West Bromwich Albioncalled Both teams to score at 52.3%live
Only the calls that landed are listed here. The rate above counts the ones that did not as well.
How these picks are made
Both teams to score, usually shortened to BTTS, means each side scores at least once in normal time. The final score and the winner do not matter, only that both goal counts are above zero. The probability on each row comes from a model trained on completed matches for this market, blended with the engine's Poisson goal model, which prices each side's chance of scoring from its attacking and defensive record.
A high number here says both defences are expected to be breached, not that the bet is good value. A price already reflects how likely a market thinks the outcome is, so the question worth asking of any row is whether the engine's probability is meaningfully above what the price implies. The track record above is the evidence for whether it usually is.
Frequently asked questions
What does both teams to score (BTTS) mean?
It is a bet that each team scores at least one goal in the match. A 1-1 draw and a 3-2 win both count as yes; a 2-0 win counts as no, however many goals the winner scored.
Is BTTS the same as over 2.5 goals?
No. Over 2.5 needs three or more goals in total, from either side. BTTS needs both sides to score. A 1-1 draw is BTTS yes but not over 2.5, and a 3-0 win is over 2.5 but not BTTS.
What does the percentage beside each pick mean?
It is the engine's probability that both teams score. It is a probability, not a guarantee: a 60% pick is expected to miss four times in ten.
Do extra time and penalties count?
No. The pick is settled on the 90-minute score, including in cup matches.
Why are some prices marked with a ≈?
No bookmaker price was stored for that pick, so the figure shown is its own fair price: 100 divided by its probability. It carries no bookmaker margin, so it is not a price anyone will pay and should not be read as value against the market.
What is the difference between live and reconstructed picks?
A live pick was stored before kick-off, so nobody could have known the result. A reconstructed pick was generated after the match from history cut off at kick-off. Both are counted, separately, and the live figure is the stronger evidence.