Raw Stats vs Underlying Numbers: How RubiScore Helps Fantasy Managers Tell the Difference

Fantasy football decisions usually pull from two different kinds of numbers: raw stats — goals, assists, clean sheets, the outcomes a scoring system actually pays for — and underlying numbers such as expected goals and expected assists, which measure the quality of a player's chances rather than the result. RubiScore publishes both categories side by side, and knowing when to trust which one is a separate skill from simply having access to the data.

What Counts as a Raw Stat in Fantasy Terms

Raw stats are the numbers a fantasy scoring engine reads directly: goals, assists, clean sheets, saves, bonus points, and minutes played. Their defining feature is that they are the literal inputs to a manager's weekly score, which makes them impossible to ignore no matter how sophisticated the rest of an analysis gets. Their limitation is equally direct — a raw stat reports what happened, not how likely it was to happen, which means a single well-taken long-range strike counts identically to a simple tap-in even though the two chances carried very different probabilities of being scored in the first place.

What Counts as an Underlying Number

Underlying numbers describe the process that produces raw stats rather than the outcome itself. Expected goals estimates the quality of a scoring chance based on factors like shot location, angle, and defensive pressure at the moment of the attempt; expected assists applies the same logic to the pass that created the chance; progressive-passing and chance-creation volume describe how often a player is involved in promising possessions at all, independent of whether any single one produced a shot. None of these numbers are paid out by a fantasy scoring system directly — their value is in what they suggest about whether a player's raw output is likely to continue, rise, or fall back toward a more typical level. RubiScore tracks both families of numbers for every player it covers, which is what makes a direct side-by-side comparison possible rather than something a manager has to assemble from separate sources.

Why the Two Categories Get Confused

Part of the reason managers default to one category over the other is that both are described, casually, as "the numbers," which flattens a real distinction. A raw stat and an underlying number can point in the same direction for a settled, in-form player, which reinforces the habit of treating them as interchangeable confirmation of the same story rather than two separate signals that happen to agree for the moment. The confusion becomes costly specifically when the two diverge — a player scoring freely despite modest underlying numbers, or one generating strong chances without goals to show for it — because that is precisely the situation where defaulting to whichever number is easier to find, usually the raw stat, produces the weaker decision.

Axis One: Predictive Power for Future Points

Over a small sample, raw stats are dominated by variance that has little to do with a player's underlying quality — a striker can go three matches without scoring while generating excellent chances, or score twice from low-quality efforts that will not repeat. Underlying numbers tend to be steadier and more predictive of near-future output precisely because they measure the process rather than a noisy result, which is why a player with strong expected-goals numbers but a quiet recent scoreline is often a better forward-looking pick than raw goal counts alone would suggest. This gap narrows considerably over a full season, where enough matches accumulate for raw output and underlying process to converge, but for week-to-week fantasy decisions the gap is exactly where the two categories diverge most.

Axis Two: Signal Speed and Sample Size

Raw stats update immediately and require no interpretation — a goal either happened or it did not. Underlying numbers need a larger sample before they stabilize into something trustworthy, since a single match's expected-goals total can be skewed by one unusually good or bad chance in a way that a rolling multi-match average corrects for. A manager reacting to one gameweek of underlying data risks the same small-sample trap that undermines reacting to one gameweek of raw output, just with an extra layer of statistical vocabulary attached. Both categories need enough matches behind them before a single number should move a decision on its own.

Axis Three: Availability and Ease of Reading

Raw stats need no explanation and appear on every scoring platform by definition, since they are the scoring inputs themselves. Underlying numbers require a data source that tracks shot-level and pass-level detail across a competition, along with some familiarity with what a "good" expected-goals or expected-assists number looks like for a given position, which is a real barrier for casual managers even when the numbers are technically available. This is the axis where raw stats have a structural, permanent advantage: they will always be easier to read at a glance, even as underlying data becomes more widely available.

Axis Four: What Each Category Misses Entirely

• Raw stats miss context entirely — they cannot distinguish a penalty conversion from a difficult curling finish, or credit a player whose good process was denied by a goalkeeper's exceptional save.
• Underlying numbers miss finishing skill and in-the-moment execution, treating two players with similar chance quality as statistically interchangeable even when one is a demonstrably better finisher over a long track record.
• Neither category captures minutes risk on its own — a player generating strong underlying numbers in twenty-minute cameos carries a different fantasy profile than one doing so across ninety, and both raw and underlying numbers need to be read alongside playing-time data to mean anything.
• Both categories are position-relative — an expected-goals total that is exceptional for a winger is unremarkable for a striker, so neither number type transfers cleanly across positions without adjustment.

When Raw Stats Should Lead the Decision

Raw stats are the right anchor when a decision genuinely hinges on very recent, position-specific scoring form and the sample is long enough to have shaken out obvious small-sample noise — roughly a run of matches rather than a single fixture. They are also the correct reference for anything that is not process-driven at all, such as clean sheets in a match where a team is expected to dominate territory but the underlying chance-quality data for the opposition is thin.

When Underlying Numbers Should Lead the Decision

Underlying numbers earn more weight exactly where raw stats are least reliable: identifying a player whose scoring form has lagged behind the quality of chances he is generating, spotting a player whose recent goals came from an unsustainable run of low-probability efforts, and comparing two players with similar raw output to see which one's underlying process suggests the output is more likely to continue. They are also more useful for early-season decisions, when raw-stat sample sizes are still thin league-wide but shot-quality data from a handful of matches already carries some signal. This is one reason RubiScore surfaces underlying-numbers views alongside the raw scoring table from the opening weeks of a season rather than waiting until a larger sample has accumulated.

A Practical Reading Order

Rather than treating this as a choice between two data types, a workable sequence runs through both in order. Start with the raw stat to see what has actually been scored or conceded. Then check the underlying number for the same window to see whether the process behind that raw output matches it, runs ahead of it, or lags behind it. Finally, cross-check playing time and role stability, since neither raw output nor underlying process means much for a player whose minutes are inconsistent from week to week. This is not a replacement for the captaincy-specific workflow built around expected goals — it is the more general framework that workflow sits inside, applicable to transfer decisions, differential picks, and squad-building as much as to picking a single captain.

The Verdict: Sequence, Not a Single Winner

Neither category is simply better, because they answer different questions — raw stats answer what has actually happened and what a scoring system will pay for, while underlying numbers answer how sustainable that output is likely to be. A practical sequence treats raw output as the scoreboard and underlying numbers as the explanation for whether that scoreboard is likely to keep looking the same, rather than picking one data type and discarding the other. RubiScore's player pages present both figures together by competition and by position, specifically so a fantasy manager can check whether a hot streak is backed by process or running ahead of it before making a transfer or captaincy call, and the platform's underlying-numbers view is built to be read alongside the raw scoring stats rather than as a replacement for them.

Both data types, broken out by player and by gameweek, are available on rubiscore.com for managers who want to compare recent raw output against the underlying numbers behind it before making a call.