What is BTTS (both teams to score)?

BTTS means both teams score at least once. Learn which scorelines qualify, which team profiles trend that way, and where the statistic misleads.

BTTS Yes means each side scores at least once; BTTS No means at least one team finishes without a goal. Who wins the match is irrelevant here. This guide shows which scorelines fall on which side, and which numbers actually matter: scoring consistency, clean sheet frequency and the home-away split, with a worked hypothetical example.

BTTS Yes — short for "both teams to score" — means that each side puts the ball in the net at least once. BTTS No is the opposite: at least one of the two teams finishes the match without a goal. The same idea is listed elsewhere as "Both Teams to Score: Yes/No", and in some countries as "GG/NG" (goal / no goal). Whatever the label, it asks one question about the game: were there goals at both ends?

Which scorelines fall on which side?

In this reading it makes no difference who wins. The only thing being counted is whether both teams scored. A 5-0 win and a 0-0 draw land on the same side of this question — in neither match did both teams get on the scoresheet.

Final score	Did both teams score?
1-1	Yes — BTTS Yes
3-2	Yes — BTTS Yes
0-0	No — BTTS No
4-0	No — BTTS No
0-1	No — BTTS No

What about own goals?

An own goal counts as a goal for the team that benefits from it, so that is the side of the scoreline it lands on. A match decided 1-0 by an own goal is still a game in which only one team has a goal to its name — the other side is left on zero.

What this statistic is actually built from

BTTS asks two separate questions at the same time: will the home side score? and will the away side score? If you cannot answer one of them with any confidence, the whole reading becomes shaky. These are the numbers worth checking:

Scoring consistency. How regularly has the team found the net recently? A steady habit of scoring tells you far more than one afternoon when four goals arrived at once.
Clean sheet frequency. A side that repeatedly keeps opponents off the scoresheet pulls its matches towards the "No" side, even when its own attack is productive.
Home and away split. A team that scores freely in front of its own crowd can look like a completely different side on the road. Read the relevant column, not the season-wide average.
Chance quality. Expected goals (xG) and expected goals against (xGA) separate genuine openings from "plenty of shots, all from distance". A team whose shot count is inflated by long-range efforts often scores less than the raw numbers suggest.
Absences and context. Two forwards missing, a heavily rotated side, or a fixture where a draw is enough for one team — all of these tend to pull goal production down.

A hypothetical example

Suppose Team A has scored in each of its last five home matches but conceded in four of them, while Team B has struggled away from home and finished three of its last five road games without a goal. These figures are invented to illustrate the logic; they are not taken from any real fixture.

Here the expectation that "Team A scores" looks well supported. But BTTS Yes also requires Team B to score. One side's scoring form cannot carry the reading on its own. Until both columns are read together — A's attack next to B's, A's defence next to B's — nothing dependable can be said about this match.

Not the same thing as Over/Under

The most common mix-up is treating BTTS Yes as shorthand for "a high-scoring game". A 1-1 draw is BTTS Yes and Under 2.5 goals at the same time. A 4-0 win is Over 2.5 and BTTS No. The two readings sit close together and often lean the same way, but they answer different questions: one counts goals, the other counts how many teams scored.

Three things that are easy to get wrong

Low odds are not a safety net. Odds show how strongly an outcome is expected; they are not a promise that the unexpected will stay away. Turning the number into a rough percentage — one divided by the odds — makes the gap between "likely" and "certain" much easier to see.
A goals-per-game average says very little about BTTS. An average of three goals per match can be produced entirely by one side scoring three every week while the other never troubles the keeper. Split the total: goals scored and goals conceded, home and away, read separately.
The story behind the table never appears in the table. A second leg, a relegation decider, a waterlogged pitch, a suspended centre-back — details like these move the goal count without ever showing up in an average.

In short

BTTS is a two-part question wearing a single label. Reading it properly means looking at both attacks and both defences, keeping home and away figures apart, and remembering that a single match is a very small sample in which almost anything can happen. The point of the exercise is not to know how the game will finish — it is to know what to look at before it starts.

Our daily match reviews on WinBall set out both teams' scoring and defensive tendencies alongside the rest of the numbers, so the two halves of this question can be read side by side.

This page is published for information only. WinBall is not a betting platform; it publishes football analysis and predictions. 18+

See the full guide

Stay one step ahead with professional football analyses and data-driven predictions.

Payments are handled securely in-app via the App Store and Google Play.

18+ · Our predictions are for information and analysis purposes only; they do not guarantee any outcome. This platform does not offer betting and does not direct users to any betting site. Illegal betting is a crime. Please act responsibly.