How to Read the Stats We Show

By the TBS Digital team · Updated 2026-08-05

Every Next Match Up preview surfaces the same set of data points, but reading them well takes a bit more than glancing at the numbers. This guide walks through each stat we show, what it actually measures, where it can mislead you if read in isolation, and how to combine it with the others for a genuinely useful pre-match picture.

Reading the H2H record

We show the last 10 meetings between two teams across all competitions, plus an aggregate win/draw/loss tally over a longer five-season lookback. The trap here is treating an old rout as equally informative as a meeting from three weeks ago. Weight recent meetings more heavily than distant ones — a 4-0 win from four seasons back, under a different manager with half the current squad, tells you far less than last month's 1-1 draw. Check the date column, not just the score column, before drawing a conclusion.

Example: if the last 10 meetings show 6 home wins but the 3 most recent meetings are all away wins, the H2H summary is stale relative to the current balance of power. The trend within the list matters more than the total.

Reading the form guide

Our form strip shows the last five results (W/D/L) across all competitions, oldest to most recent, left to right. A run like W-W-W-D-L looks strong at a glance, but the quality of opposition inside that run matters enormously — three wins against relegation-threatened sides read very differently from three wins against top-six opposition. We don't weight form by opponent strength in the strip itself (it would make an already-dense card harder to parse), so cross-reference the form strip against the relevant league table to judge opponent quality yourself.

Also worth noting: because form includes cup and European fixtures, a team resting key players for a domestic cup tie against lower-league opposition can post a scrappy draw or even a loss that has little bearing on their league form. Read the competition context alongside the letter sequence, not the letters alone.

Reading xG (expected goals), where available

xG estimates the quality of scoring chances created, independent of finishing. A team that wins 1-0 with 0.4 xG against and 2.1 xG for actually dominated the underlying play, while a team that wins 1-0 with 1.8 xG against and 0.5 xG for got a fortunate result that a longer run of matches would likely correct. We only display xG where reliable shot-level data exists for that competition — if the column is missing on a match page, it's because we don't trust the underlying data for that league or season, not because the number is being withheld.

Use xG as a longer-run signal, not a single-match verdict. A team can lose a match while heavily outperforming on xG and still be the "better" side in a way that predicts their next several results more reliably than the scoreline of that one game.

Matchday context: what round, what's at stake

The same fixture carries different weight depending on where it falls in the season. A meeting in matchday 3 with both squads at full strength and nothing yet decided reads differently from the same fixture in matchday 36 with one side already relegated and fielding reserves. We show the matchday number and competition stage on every match card specifically so you can judge motivation and squad rotation risk — a team with nothing left to play for is statistically more likely to rotate, rest key players, and underperform their season-long form.

Referee stats and disciplinary tendencies

Where we display referee data, it's typically cards-per-game and penalty-award frequency drawn from that official's recent match history. A referee who averages notably more yellow cards per match than the competition norm makes a tight, physical fixture more likely to see red cards or key suspensions carry into the next round. This is a secondary signal — it doesn't tell you who wins — but it's useful context for injury-time drama or a match that turns on a red card. As with squad news, we hide this section on match pages where we don't have reliable data for the appointed official, rather than fill it with a league-wide average that wouldn't represent that specific referee.

Injury impact: read who, not just how many

A squad news section listing "3 players unavailable" means very different things depending on which three. Losing a squad's first-choice goalkeeper and both starting centre-backs is a much bigger deal than losing a fourth-choice striker, a backup full-back, and a youth-team player who wasn't going to feature anyway. We list confirmed unavailable players by name and position specifically so you can judge the real impact rather than relying on a raw count. As covered in our FAQ, official squad news is often confirmed close to kick-off, so this section may be blank on a match page you check a day or two out — it will populate once lineups firm up.

Home and away splits

Aggregate season form flattens a distinction that matters a lot: some teams are genuinely different sides at home versus away, with home-form win rates 20-30 percentage points higher than their away-form win rate being common even among mid-table clubs. When you check an upcoming fixture's form strip, note the venue split rather than reading pure aggregate form — a team on a poor run overall but with a strong home record specifically is a different proposition hosting a match than the same team traveling away.

Converting kick-off times across time zones

Every match card shows two times: the venue's local time with explicit UTC offset (for example, 20:00 CEST / UTC+2), and your browser's auto-detected local time. If you're sharing a kick-off time with someone in a different time zone, always quote the UTC offset rather than a bare local time — "8pm" is ambiguous the moment two people are in different zones, but "20:00 CEST / UTC+2" is not. This matters especially around daylight saving transitions: European clocks change on different dates than UK clocks in some years, and a one-hour miscalculation across that gap is the single most common way fans miss a kick-off.

Worked example: a 15:00 UTC+1 kick-off in London is 16:00 in Paris (UTC+2 during the same period if France has already shifted to summer time, or 16:00 UTC+1 if not — check the explicit offset, don't assume both countries change on the same date), 10:00 in New York (UTC-4, Eastern Daylight Time), and 23:00 the same day in Tokyo (UTC+9). Always do the arithmetic from the UTC offset, never from one country's local convention to another's directly.

Putting it together

No single stat on a Next Match Up preview is meant to stand alone. A useful pre-match read combines recent H2H trend, current form with opponent-quality context, matchday stakes, and — where available — xG and injury news, weighted differently depending on the specific fixture (see our worked examples for how that weighting shifts fixture by fixture). We deliberately don't synthesise these into a single prediction or score ourselves — that's a design choice, not a limitation — so the synthesis is yours to make with the full picture in front of you.

Related reading: how we compile this data · sample H2H analyses · glossary · FAQ

Ask ChatGPT▾ about football

This weekend's best fixtures→How to read head-to-head stats→Biggest football rivalries→