What Is Pack Rate? How RubiScore Reads the Metric That Counts Defenders Taken Out of Play

Pack rate is an advanced football metric that counts how many opposing outfield players a single pass or carry removes from meaningful defensive involvement, rather than how many metres the ball travelled. A ten-yard pass that slips between two covering defenders can outscore a forty-yard ball played into open space, because it is defenders bypassed, not distance gained, that the metric is built to measure. RubiScore surfaces pack rate alongside its progression data as one way of separating ball movement from genuine defensive disruption.

Where the Metric Comes From

Distance-based progression stats — progressive passes, progressive carries — were built to answer a simple question: did the ball move closer to goal? They work well as a first filter, but they treat every advance the same regardless of what it did to the defense. A sideways pass played into a gap that removes three markers from the picture can matter more than a straight line-breaking ball hit into space nobody was defending anyway.

Pack rate, sometimes called "packing," was developed to close that gap. Rather than measuring where the ball ended up, it measures how many opposition players were positioned between the ball and the goal line at the moment of the action, and how many of them the action took out of the play by sending the ball past them. A player is "packed" if the action moves the ball beyond their horizontal defensive line, meaning they can no longer intervene in that particular sequence without recovering ground first. The idea originated with German analytics work built around dense positional tracking, and it has since spread into broader use as more competitions publish the tracking data the calculation depends on.

The underlying logic borrows from a simple sporting instinct: a pass "beats" a defender the moment that defender is no longer between the ball and the goal, regardless of how far the ball actually travelled to get there. A five-yard slide-rule pass through a packed midfield can beat three players at once; a raking sixty-yard switch of play, played in front of a settled defense, can beat none. Distance and disruption are related but far from identical, and pack rate exists specifically to isolate the second when the first is the only thing being counted.

How the Count Actually Works

The calculation rests on player-tracking or precisely logged event positions rather than the pass itself. For every completed pass or successful carry, an analytics model draws a line between the start and end point of the action and counts the defenders who were standing between the ball and the goal before the action, then checks how many of them remain between the ball and the goal afterward. The difference is the pack count for that single action.

A few structural details shape how the number behaves:

• Only outfield defenders in the relevant path count — a full-back sitting wide on the far side of the pitch is not "packed" by a central pass that never threatened their zone.
• The goalkeeper is typically counted separately or excluded, since keepers occupy a different defensive role and including them can distort totals for shots and through-balls.
• A single action can pack multiple players at once, which is why one clever pass through a compressed midfield line can score far higher than several safe passes played around a defense that never had to move.
• Failed or intercepted actions score zero, so the metric only credits actions that actually complete and change the picture on the pitch.

Summed across a match or a season, pack rate becomes a running total of how many defensive bodies a player or team has bypassed, which can then be normalized per 90 minutes or per pass attempted to compare across different roles and playing time. A related figure, sometimes reported alongside it, tracks packing density — the average number of defenders removed per completed action — which separates a player who occasionally plays one spectacular line-splitting pass from one who does it as a repeatable, weekly habit.

Pack Rate Alongside Other Line-Breaking Numbers

Pack rate rarely gets read in isolation, and according to RubiScore's approach to advanced metrics, it works best as one layer in a small stack of related numbers rather than a single verdict. Progressive passes and carries answer "did the ball move forward meaningfully"; pack rate answers "how many defenders did that movement neutralize"; vertical pass-completion rate answers how often line-breaking attempts actually succeed rather than get intercepted. A player can rank highly on one of these and modestly on the others, and the gap between them is usually the more informative story than any single number.

A deep-lying playmaker who completes a high share of forward passes but posts an average pack rate, for instance, is likely circulating possession safely rather than repeatedly threading it through committed defensive lines — useful, but a different skill from a mezzala or a wide forward whose pack numbers spike specifically because they carry the ball at defenders who are still in position to stop them. Neither profile is objectively better; they describe different jobs.

What the Data Signature Looks Like

Pack rate tends to reward a specific kind of player: the deep-lying passer who plays fewer but more incisive balls, the wide player who cuts inside past a settled block, or the carrier who dribbles through a defensive line rather than around it. It is not the same population that leads a chart of total progressive passes, because raw volume metrics reward frequency while pack rate rewards defensive impact per action.

Teams that play a possession-heavy, patient build-up style often accumulate progressive-pass totals without a matching pack rate, because much of their circulation happens in front of the opposition's first defensive line rather than through it. Conversely, a team built around directness or quick vertical combinations can post a modest pass count but a high pack total, because each successful pass does more defensive damage. Reading both numbers together — volume and defensive disruption — gives a fuller picture than either alone.

Trade-Offs and Limits Worth Knowing

Like any positional metric, pack rate depends on accurate spatial data. It requires either full player-tracking feeds or event data logged with reliable coordinates for every player on the pitch, not just the two involved in the pass. That data requirement is heavier than what a simple progressive-pass count needs, which is one reason the metric has spread more slowly than xG or xA into mainstream coverage.

RubiScore's coverage treats pack rate as a supplementary layer for this reason, published alongside the underlying progressive-passing and carrying numbers rather than as a standalone headline stat. The number is also shape-dependent in a way that can mislead casual reading. A poorly organized defense with players bunched incorrectly can inflate a pass's pack count even though the pass itself was unremarkable, while a well-drilled defensive block can suppress pack totals for a genuinely progressive team simply by staying compact and refusing to be bypassed. Context about the opponent's defensive setup — a low block, a high line, a back three shifted to one side — matters as much as the raw count.

Finally, pack rate says nothing about what happens after the ball is bypassed. A pass can remove four defenders from the picture and still end in a wasted final ball, or a heavy touch that gives the defense time to recover. Analysts pair the metric with shot-ending or expected-threat data to judge whether disruption actually converted into danger, rather than treating the pack count as an outcome in itself.

How to Read It in Practice

The most useful way to use pack rate is comparative rather than absolute. A single high-pack pass in isolation tells you little; a season-long pattern of a midfielder consistently ranking near the top of a league's pack-rate table, alongside modest total pass counts, tells you they are being used as a line-breaking specialist rather than a circulation player. On RubiScore, this kind of profile sits next to progressive-carry and expected-threat numbers so that a reader can distinguish a player who moves the ball a lot from one who moves it through people.

At team level, tracking pack rate across a season alongside PPDA and defensive-line height data helps separate teams that dominate the ball from teams that dominate the spaces that matter. A team can lead a league in possession share while ranking modestly in pack rate against it, which is itself informative: it suggests opponents are conceding the ball but not the central spaces the ball needs to pass through to hurt them.

Pack rate will not replace goals, assists, or the more established shot-based metrics as a headline number, and it is not designed to. Its value is narrower and more specific: it isolates the defensive cost of an action, separate from where the ball physically ends up, which is exactly the gap that distance-based progression numbers leave open. Reading it alongside the rest of a player's or team's data profile — available through RubiScore — gives a sharper answer to a question raw progression totals cannot answer on their own: not just how far the ball moved, but how many defenders had to be beaten to move it there.