Profiling a striker means measuring far more than how many goals they score. RubiScore builds a striker profile from several layers of data — finishing quality, chance creation, link play, and off-ball work — to describe not just how productive a forward is, but what kind of forward they actually are. Goals are the headline; the profile is the story underneath it.
A goal tally is the most visible striker statistic and the least complete. Taken on its own, it flatters and deceives in equal measure. A forward who takes penalties has an inflated total against one who does not. A striker in a dominant team feeds on a steady supply of chances, while an equally skilled forward in a weaker side may go weeks without a clear sight of goal. Short streaks distort everything, because finishing is volatile across small samples.
The point is not that goals do not matter — they decide matches — but that a goal count answers only one narrow question. To understand a striker, you have to ask what they did to arrive at that number, and what they contributed when they did not score. That is the gap a structured profile is built to close.
A useful way to read a centre-forward is in layers, working outward from the goal itself. Each layer answers a different question:
No single layer defines a striker. Read together, they separate a poacher from a creator, a target man from a false nine, a finisher from an all-round forward.
Expected goals sits at the centre of any modern finishing assessment. xG assigns every shot a probability of scoring based on factors such as distance, angle, and the type of chance, so a striker's cumulative xG describes the quality of openings they reach. Comparing actual goals against that figure is where it becomes revealing.
RubiScore tracks both numbers side by side. A forward who consistently scores more than their xG over a large sample may be an elite finisher — or may be riding a hot run that regression will eventually correct. A striker scoring below their xG might be finishing poorly, or might simply be unlucky over too few shots. The discipline is to wait for the sample to grow before drawing a conclusion, because finishing variance is large and fast judgements are usually wrong.
Many of the most valuable forwards create as much as they finish. A striker who drops to link play, slips in a runner, or draws defenders to free a teammate is contributing in ways a goal column never shows. Key passes, expected assists, and passes completed in the final third capture that side of the game.
This is where profiling separates similar-looking scorers. Two forwards with the same goal total can be completely different players: one a pure penalty-box finisher who barely touches the ball outside it, the other a deep-dropping creator who knits the attack together. A profile that records creation alongside finishing makes that distinction visible instead of leaving it to impression.
The hardest part of a striker's game to quantify is what they do without the ball, and it is often the most important. Off-ball movement — the runs that stretch a defence or create space for others — rarely shows up directly in a stat line, but positional and heat-map data reveal where a forward operates and how they pull defenders around.
Pressing is the other overlooked layer. Modern centre-forwards lead the defensive effort, and metrics for pressures and defensive actions in the attacking third describe how much work a striker does when possession is lost. RubiScore surfaces these alongside the attacking output so that a profile is not just a record of shooting, but a fuller picture of a forward's contribution across both phases.
When the layers are read together, forwards tend to fall into recognisable types, each with its own statistical signature:
These are not rigid boxes, and many forwards blend two or three of them across a season. But naming the type is a useful first read, because it tells you what a striker is built to do before you judge how well they do it.
Pulling the layers together, a striker profile on the platform is built to describe a complete forward rather than a single number. Across the matches it covers, it brings together:
Because these are stored per player and normalised to a per-90-minute basis, RubiScore lets a substitute be compared fairly with an ever-present, and a forward in one competition with a forward in another. The profile is designed to travel with the player as context, not to live and die with a single match.
The framework only works if the comparison is honest, and a few rules keep it that way:
Applied together, these turn a pile of statistics into a fair reading of what a forward actually offers.
Even a complete profile has boundaries, and reading it well means respecting them. Data describes what happened, not always why it happened: it can record that a striker under-performed their xG without knowing whether the cause was finishing, fortune, or the pressure of the moment. Numbers struggle to capture intelligence of movement, leadership, and the decisions that never end in a recorded action. And small samples remain treacherous, because a striker's output swings far more violently week to week than a defender's or a midfielder's.
Used with those caveats, a striker profile becomes a tool for understanding rather than a verdict to quote. The full set of finishing, creation, and off-ball data sits alongside the wider match, club, and competition layers at rubiscore.com, where a forward's profile is updated as each fixture unfolds.