Account
Language
Time Zone
COEF
BTTS Predictions Yesterday
Review yesterday's Both Teams to Score predictions on Betiball and compare the original BTTS Yes and No probabilities with the final score of each completed fixture. The historical view shows what the model estimated before kick-off, whether both teams actually scored and whether the leading BTTS prediction was correct.
Use the completed matches below to review yesterday's results or explore all football predictions from yesterday, yesterday's Under/Over 2.5 results, BTTS predictions today, BTTS predictions tomorrow and all Both Teams to Score predictions.
2026-09-18
Quy Nhon United vs Ho Chi Minh City - Prediction & Odds
2026-09-18
Brentford vs Chelsea - Prediction & Odds
2026-09-18
RCD Espanyol vs Elche - Prediction & Odds
2026-09-18
Bayern Munchen vs Union Berlin - Prediction & Odds
2026-09-18
Philippines U23 vs Vietnam U23 - Prediction & Odds
2026-09-18
Kuwait U23 vs Uzbekistan U23 - Prediction & Odds
2026-09-18
Saudi Arabia U23 vs Qatar U23 - Prediction & Odds
2026-09-18
Monza vs Sassuolo - Prediction & Odds
2026-09-18
Monaco vs Lens - Prediction & Odds
2026-09-18
Arema FC vs Persik Kediri - Prediction & Odds
2026-09-18
Madura United vs PSIM Yogyakarta - Prediction & Odds
2026-09-18
New York City FC vs New York Red Bulls - Prediction & Odds
2026-09-18
Ayutthaya United vs Uthai Thani FC - Prediction & Odds
2026-09-18
Yate Town vs Chippenham Town - Prediction & Odds
2026-09-18
Worcester City vs Stratford Town - Prediction & Odds
2026-09-18
Zhejiang Professional FC vs Wuhan Three Towns - Prediction & Odds
2026-09-18
Bristol City vs Watford - Prediction & Odds
2026-09-18
Groningen vs PEC Zwolle - Prediction & Odds
2026-09-18
Atletico Bucaramanga vs Dep.Independiente Medellin - Prediction & Odds
2026-09-18
Aguilas Doradas vs Deportivo Pereira - Prediction & Odds
Yesterday's Both Teams to Score Results
This page provides a historical view of completed BTTS predictions rather than a forecast for upcoming matches. Each settled fixture should preserve the Yes and No probabilities available before kick-off and compare them with the final score.
BTTS Yes means both teams scored at least once during the relevant match period. BTTS No means one or both teams failed to score.
| Final Score | BTTS Result |
|---|---|
| 0-0 | No |
| 1-0 | No |
| 0-2 | No |
| 1-1 | Yes |
| 2-1 | Yes |
| 2-3 | Yes |
Predicted BTTS Outcome vs Actual Result
The central historical comparison is between the probability distribution published before the match and what actually happened after kick-off.
| Field | Historical Meaning |
|---|---|
| BTTS Yes % | Original probability that both teams would score |
| BTTS No % | Original probability that at least one team would fail to score |
| Prediction | The higher-ranked Yes or No outcome before kick-off |
| Final Score | The completed match score |
| Actual BTTS | Yes or No based on the final score |
| Prediction Result | Correct or Incorrect |
What Counts as a Correct BTTS Prediction?
A BTTS prediction is correct when the leading Yes or No selection matches the settled result of the fixture.
Correct BTTS Yes
If Yes carried the higher probability before kick-off and both teams later scored, the selection is correct.
Correct BTTS No
If No was the leading prediction and at least one team finished without scoring, the selection is correct.
The winner does not matter
A 1-1 draw, 3-1 home win and 1-4 away win all produce BTTS Yes because both teams scored.
Why the Original Yes and No Probabilities Should Remain Visible
A Correct or Incorrect label alone does not show how strongly the model favoured the selected outcome.
| Original Prediction | Actual Result | Interpretation |
|---|---|---|
| Yes 78% / No 22% | No | A relatively surprising model miss |
| Yes 52% / No 48% | No | A very closely balanced forecast |
Both leading selections are technically incorrect, but the second match was far more uncertain before kick-off.
Show the Probability Originally Assigned to the Actual Outcome
For a completed fixture, it is useful to show not only whether the leading selection was correct but also the probability that the model originally assigned to the outcome that actually occurred.
| Pre-Match Forecast | Final Score | Actual BTTS | Original Probability |
|---|---|---|---|
| Yes 67% / No 33% | 2-0 | No | 33% |
| Yes 44% / No 56% | 2-1 | Yes | 44% |
The figures above are illustrative examples rather than current Betiball match results.
Which Team Failed to Score Adds Useful Detail
A BTTS No result can happen in several different ways. Identifying which side failed to score provides more information than the No label alone.
| Final Score | BTTS | Scoring Failure |
|---|---|---|
| 0-0 | No | Both teams failed to score |
| 0-2 | No | Home team failed to score |
| 3-0 | No | Away team failed to score |
| 2-1 | Yes | Neither team failed to score |
This makes the historical data more useful when reviewing how well the model estimated each team's individual scoring probability.
Individual Team Scoring Probabilities Explain the BTTS Forecast
If Betiball stores separate pre-match scoring probabilities for the home and away teams, these values should remain available on historical fixtures.
BTTS Yes requires both teams to contribute at least one goal, so identifying the weaker scoring side can help explain why the original Yes probability was high or low.
Home scoring probability
This estimates the likelihood of the home side scoring at least once.
Away scoring probability
This estimates the likelihood of the visiting team finding the net.
Actual scoring outcome
Historical settlement can then show whether each team's individual scoring expectation was realised.
A BTTS No Result Can Still Be High-Scoring
BTTS is not a total-goals market. A match can produce several goals and still finish No if all goals are scored by one team.
| Score | Total Goals | BTTS |
|---|---|---|
| 3-0 | 3 | No |
| 4-0 | 4 | No |
| 5-0 | 5 | No |
BTTS Yes Can Still Finish Under 2.5
Likewise, both teams can score without the match producing at least three goals.
A 1-1 result contains two goals, so it settles BTTS Yes and Under 2.5.
| Score | BTTS | Under/Over 2.5 |
|---|---|---|
| 1-1 | Yes | Under |
| 2-1 | Yes | Over |
| 3-0 | No | Over |
| 0-0 | No | Under |
For the separate total-goals audit, review Under/Over 2.5 Predictions Yesterday.
The Final Winner Does Not Define the BTTS Result
BTTS asks whether both teams scored rather than which side won.
| Final Score | 1X2 Result | BTTS |
|---|---|---|
| 1-0 | Home | No |
| 2-1 | Home | Yes |
| 1-1 | Draw | Yes |
| 0-0 | Draw | No |
| 0-2 | Away | No |
| 1-3 | Away | Yes |
Review Home, Draw and Away performance separately at 1X2 Predictions Yesterday.
Expected Goals Can Be Compared with Actual Team Scoring
If pre-match expected-goals values are stored, yesterday's fixtures can help show whether each team's attacking expectation translated into an actual goal.
High xG expectation but no goal
A team can create strong opportunities without converting them, causing an otherwise plausible BTTS Yes forecast to fail.
Low xG expectation but a goal
A team can score from limited opportunities or convert a low-frequency chance.
Both teams create and score
When both underlying opportunity profiles and the final score point in the same direction, the historical result provides a more complete picture of the fixture.
Expected goals should remain supporting context rather than be substituted for the actual scoring result.
Clean-Sheet Outcomes Add Another Historical Layer
Every BTTS No result necessarily contains at least one clean sheet under the simple final-score definition.
Home clean sheet
The away side failed to score.
Away clean sheet
The home side failed to score.
Double clean sheet
A 0-0 result means both teams kept a clean sheet.
Historical clean-sheet outcomes can be compared with the pre-match defensive probabilities if those values are available in Betiball's model data.
BTTS Accuracy Should Be Split Between Yes and No
A single global hit rate can conceal whether the model performs differently when selecting Yes and No.
| Prediction Type | Recommended Historical Measures |
|---|---|
| BTTS Yes | Selections, correct results, accuracy and average probability |
| BTTS No | Selections, correct results, accuracy and average probability |
This makes it easier to identify whether one side of the model is consistently over- or underestimated.
Daily Accuracy Needs a Visible Sample Size
An accuracy percentage has limited meaning without the number of settled fixtures used to calculate it.
Yesterday's summary should therefore show the total number of eligible predictions alongside correct and incorrect outcomes.
Settled predictions
Include fixtures with a valid final BTTS result.
Correct predictions
Count all eligible Yes and No selections that matched the result.
Incorrect predictions
Keep unsuccessful predictions in both the results table and headline calculation.
Unresolved matches
Do not include fixtures without a valid settlement in the accuracy denominator.
Confidence Gap Shows How Strong the Yes or No Preference Was
Because BTTS is a two-outcome probability distribution, the distance between Yes and No can provide an intuitive indication of how strongly the model preferred one side.
A simple historical Confidence Gap can be calculated as:
Confidence Gap = Higher BTTS Probability − Lower BTTS Probability
| Prediction | Confidence Gap |
|---|---|
| Yes 74% / No 26% | 48 pts |
| Yes 53% / No 47% | 6 pts |
| No 68% / Yes 32% | 36 pts |
The examples show presentation logic only.
Accuracy by Probability Band Provides Better Model Context
Grouping yesterday's predictions with a larger historical dataset can show whether higher-probability BTTS forecasts actually settle more frequently.
| Leading Probability | Historical Interpretation |
|---|---|
| 50% to 54% | Closely balanced forecast |
| 55% to 64% | Moderate preference |
| 65% to 74% | Strong preference |
| 75%+ | Highest-probability group |
The useful test is not the label itself but whether observed results improve as the model's probability rises.
Calibration Tests More Than Correct and Incorrect Picks
A probabilistic BTTS model should not be evaluated solely by the percentage of leading selections that finished correctly.
Across a sufficiently large sample, matches assigned approximately 70% probability to BTTS Yes should produce Yes more often than matches assigned around 55%.
The same principle applies to BTTS No. If high-confidence forecasts repeatedly settle much less often than the stated percentages imply, the probabilities may be too aggressive.
One Day Is Not Enough to Judge BTTS Performance
Yesterday provides a useful transparency layer but remains only one matchday.
Penalty incidents, dismissals, unusually strong goalkeeping, finishing variance and other football events can materially alter individual results.
Daily results are therefore best accompanied by rolling historical samples.
Last 7 days
Useful for monitoring recent model behaviour.
Last 30 days
A broader sample reduces the effect of one unusual matchday.
Last 90 days
Provides stronger evidence where model methodology has remained sufficiently comparable.
League-Level BTTS Results Can Reveal Different Baselines
The frequency with which both teams score can vary between competitions, making league-level reporting useful where sample size is sufficient.
Observed BTTS Yes rate
This provides historical context for how frequently both teams scored in the competition.
Model Yes probability
Historical predictions can be compared with the eventual result frequency rather than simply assuming a universal football baseline.
Competition-specific accuracy
Breaking results down by league can reveal differences that disappear inside one global accuracy figure.
Home and Away Scoring Errors Can Be Diagnosed Separately
A missed BTTS prediction can be broken down further to identify which team's scoring outcome differed from expectation.
Home team predicted to score but failed
This can be recorded separately from an away-side scoring miss.
Away team predicted to score but failed
The same distinction helps reveal whether away scoring probability is systematically too high or too low.
Unexpected scorer from a low-probability side
A BTTS No prediction can fail because the weaker attacking team scores even when the stronger side performs as expected.
These diagnostics are more useful across large samples than on individual fixtures.
Recent Goal Streaks Should Not Rewrite Historical Predictions
Once the final score is known, it is easy to explain the outcome with hindsight. A credible historical page should instead preserve what the model actually estimated beforehand.
Keep the original Yes and No percentages
Do not recalculate them using the known final score.
Keep the original selection
An incorrect Yes or No prediction should remain visible.
Add the result afterwards
Final Score and Actual BTTS should sit beside the original prediction rather than replace it.
Preserve the timestamp
This shows when the prediction was published or last updated before kick-off.
Prediction Revisions Should Remain Auditable
BTTS probabilities can change before kick-off when new information becomes available. If Betiball stores multiple versions, these should not be silently collapsed into a rewritten historical forecast.
The final valid pre-match version can be used for headline settlement while earlier versions remain available for deeper model auditing.
This is particularly useful where confirmed line-ups materially changed either team's expected scoring probability.
First-Half BTTS and Full-Match BTTS Are Different Events
A 0-0 interval does not determine the full-match BTTS result. Both teams can still score after the break.
Likewise, if the first half finishes 1-1, full-match BTTS Yes has already been satisfied under the ordinary full-match definition.
| HT Score | FT Score | Full-Match BTTS |
|---|---|---|
| 0-0 | 1-1 | Yes |
| 0-0 | 2-0 | No |
| 1-1 | 2-1 | Yes |
Match Status Must Be Final Before Ordinary BTTS Settlement
Historical accuracy should be calculated only from fixtures with a valid result under Betiball's stated match-period rules.
Postponed
A fixture that never started should not count as a BTTS result.
Cancelled
A cancelled match should remain outside the settled accuracy calculation.
Abandoned
The score when play stops should not automatically be treated as the final BTTS outcome unless the site's settlement methodology explicitly says otherwise.
Suspended
A match expected to resume should remain distinct from a completed fixture.
Extra Time Requires a Clearly Defined Scoring Period
For knockout fixtures, the BTTS prediction should clearly state whether it applies only to the normal match period or includes another defined period.
If Betiball's standard prediction concerns regulation time, goals scored later in extra time should not retrospectively change the historical Yes or No result.
The same definition should be used consistently before the match and when yesterday's predictions are audited.
Browse BTTS Predictions Across Matchdays
Review Other Football Prediction Results from Yesterday
| Prediction Market | Historical Review |
|---|---|
| 1X2 | Home, Draw and Away results |
| Live 1X2 | Historical in-play probability movement |
| Under/Over 2.5 | Total-goal prediction results |
| Half Time | First-half result predictions |
| Half Time/Full Time | HT-to-FT match-path predictions |
| Double Chance | 1X, X2 and 12 results |
| Asian Handicap | Handicap settlement results |
| Goalscorers | Player scoring prediction results |
| Corners | Corner prediction results |
| Cards | Card prediction results |
How Yesterday's BTTS Performance Should Be Reported
A trustworthy historical record should apply the same calculation method to every eligible match rather than selecting only favourable results.
Include every settled prediction
All eligible Yes and No forecasts should remain in the historical dataset.
Keep unsuccessful predictions visible
Incorrect selections are necessary for meaningful performance reporting.
Preserve both probabilities
Yes and No percentages should remain available even when only one was the leading selection.
Record the actual result
The final score and settled BTTS outcome should be shown beside the original prediction.
Show probability of the actual outcome
This helps distinguish a genuinely surprising result from an alternative that already carried substantial probability.
Display sample size
Every accuracy figure should state how many settled predictions were used to calculate it.
Common Questions About Yesterday's BTTS Predictions
What does BTTS mean?
BTTS means Both Teams to Score.
What does BTTS Yes mean?
Both teams must score at least once during the relevant match period.
What does BTTS No mean?
At least one of the teams finishes without scoring.
Is 1-1 BTTS Yes?
Yes. Both teams scored.
Is 3-0 BTTS Yes?
No. Only the home team scored.
Is 0-0 BTTS No?
Yes. Neither team scored.
Is BTTS the same as Over 2.5?
No. A 1-1 result is BTTS Yes but Under 2.5, while 3-0 is BTTS No but Over 2.5.
Can a BTTS Yes prediction be correct if the away team wins?
Yes. Any score in which both sides score qualifies, such as 1-2 or 2-3.
Can a 70% BTTS prediction still lose?
Yes. A probability below 100% always leaves room for the alternative outcome.
Why preserve yesterday's Yes and No percentages?
Keeping the original distribution makes it possible to evaluate model confidence, accuracy and calibration after the result is known.
Should extra-time goals count?
Only if the prediction explicitly defines extra time as part of the relevant scoring period. Historical settlement should follow the same definition that applied before kick-off.
Where can I find today's BTTS forecasts?
Visit BTTS Predictions Today.
Official Goals Determine the Historical Score
The BTTS result ultimately depends on whether each side has at least one recognised goal during the defined match period. Football's Laws of the Game establish when a goal is awarded and how the match result is determined.
For the official framework, see IFAB Law 10 – Determining the Outcome of a Match.
The historical BTTS result should use the official match score supplied by the relevant competition or reliable match-data source rather than infer the outcome from unofficial event information.
Historical BTTS Accuracy Does Not Guarantee Future Results
Betiball provides statistical football analysis and probability estimates rather than guaranteed outcomes. Yesterday's completed predictions can help users review historical performance, but they cannot determine whether both teams will score in a future fixture.
Learn more about Betiball through About Us, FAQ, Terms of Use, Privacy Policy, Avoid Scam and Contact Us.
If you choose to gamble, only do so where legal and if you meet the applicable age requirements. Historical prediction performance should never be treated as a guarantee of future results. See Responsible Gaming for further information.