How your rating works

Start with the plain-English version below. The complete master equation, full pseudocode, every constant and the trained weight tables follow further down. Values shown are the parameters currently deployed.

The short version

1 · The bar. Before grading anyone the engine predicts the match: team skill, who's attacking, bots, console share, premades, new players, this map's quirks — and where the matchmaker put you. Battle rating runs BR 1–5, and what counts is whether you were placed above the BR you brought: an up-tier is something done to you, so it lowers the bar. That prediction E is the bar — win as the heavy favorite and the result barely moves you; upset strong odds and it pays.

Your equipment does not rate you. Bringing better gear never raises your rating and bringing worse gear never lowers it. The only BR question the engine asks is the up-tier one above.

2 · The grade. Win and it's 70% how you played, 30% that you won. Lose and the stat line counts 60%, the result 40% — so a pretty scoreboard can soften a loss but rarely erase it. And the stat line is judged against what players of your rating usually score in a lobby like this: topping a weak lobby is what the engine expects of a strong player, so it pays little; doing it in a strong lobby pays in full. "How you played" is 17 stats, each measured against your own lobby and weighted by your job that match — and dying while DEFENDING costs nothing by itself (defenders don't burn tickets; the penalty measured as noise). Valves: losing records get their stat credit damped, blowout winners aren't punished for coasting, and a newcomer's stat line counts less for their first 8 games (from 75% of its usual weight).

3 · The move. Step size scales with uncertainty squared — new players swing, veterans barely move. Your uncertainty also shrinks with matches played, so a long record can't keep swinging just because your lobbies were one-sided. If you lost and the math still says "up", the gain is cut to 70% — losing is never a good way to climb. First 10 games clamped to ±75; skill estimate never goes below 200.

4 · Deserting. Leave a match more than a minute after you first spawn and it counts as a loss your stats can't soften, even if your team goes on to win. Leave within the first minute, or before spawning, and the match isn't rated. That is the whole rule: the quit costs you once, and nothing follows you into later matches. It applies to matches from 5 October 2026 on; in older matches a quit counted as a loss only after a third of the match. If every real player on one team has left, the match isn't rated for anyone — nobody takes a loss, and nobody gets a win against an empty team.

5 · The ladder. Ranked by μ−2σ, experience-shrunk — a confidence statement: "you're at least this good." Tiers are daily percentiles of the same number, so tier and rank can't disagree.

6 · Two ladders. Matches with at least one PC player rate on the Main ladder; matches without PC players (all-console lobbies) rate on the Console ladder only. The relationship is one-way: a console player's games against PC players still inform their Console rating, but console-only games never touch the Main ladder — so a Main-ladder rank is always earned against the PC player pool. Console players carry both ratings; tiers are cut separately within each ladder.

Common questions

I lost but gained points — bug?
Rarer now, and deliberately small. In a loss the grade is only 60% performance (vs 70% in a win), and any upward move a loss does produce is cut to 70% on top. You can still eke out a few points by dominating a lobby as a heavy underdog — but losing streaks no longer climb the ladder.
Do deaths on defense hurt me?
Not directly. Since the 0.7.6.53 update (29 September 2026) defenders have a ticket pool too, so a defender death is a real cost. We re-fitted on the matches after the update, and the result held: adding a death or squad-death penalty on defense, or moving the attacker-side offsets, still made predictions worse in both halves of the test window. Defense deaths stay unscored for now.
Why is a worse K/D above me?
More proven games (smaller σ, less shrink), more wins, or value in the other stats. K/D itself isn't scored: it mostly repeats kills and deaths.
Why did my first games move me so much?
σ starts at 377 — fast learning on purpose, capped at ±75/match for 10 games.
My rating jumped around on 4–5 October 2026 — what happened?
The rules for leaving matches changed twice, and each change re-rated every match on record. On 4 October a rule went live that stopped crediting wins to players who had recently left many matches. It turned out to make those wins cost rating, and the lost points stayed long after the leaving stopped — some players dropped around 300 overnight. That rule was withdrawn the same day and those points were restored. The rule now is the one in section 4 above: a quit costs once, when it happens, and only in matches from 5 October on.
A match shows no rating change for me — why?
Four possible reasons. You left before spawning or within a minute of your first spawn (before 5 October 2026: before a third of the match). Every real player on one team left, which un-rates the match for everyone. The replay had no readable winner. Or you played it incognito, which never moves a rating.
I crashed or had to leave — do I lose rating?
If it was more than a minute after your first spawn, yes: it counts as one loss, the same as any other. A replay can't tell a crash from a quit. It costs you that one match and nothing afterwards — there is no penalty that builds up or follows you into later matches.
Can I farm bots?
Bot-heavy lobbies lower the bar E, and stats are z-scored against your own lobby, which farms the same bots.
Do new players on my team cost me rating?
No — they lower the bar. A brand-new player is rated at the average of established players (those with 20+ rated matches) minus 25, so a first match starts a little under the typical player instead of at a fixed number. First matches are still won about 44% of the time, not 50%. So every player with few rated matches lowers their own side's expected win chance, most on a first match and fading out over roughly their first 20. A lower bar means a loss with new teammates costs you less and a win pays more. It changes the prediction only: nobody's rating is moved for being new, or for playing beside someone who is.
Does my equipment BR matter?
No. The engine asks exactly one BR question: were you placed above the BR you brought? Battle rating runs BR 1–5. If the lobby's BR is higher than yours you were up-tiered — the matchmaker did that to you, so the bar drops. Matched at your own BR, the term is simply zero.

It is deliberately a placement flag, not a gear score. Because Enlisted matches within about one BR, the comparison is capped at one tier either way: bring BR 1 into a BR 5 lobby and you are graded as BR 4, never credited for a two-tier gap the matchmaker cannot create. Under-bringing is your choice, so it is never rewarded — and at the ends of the scale the question is one-sided: in a BR 5 lobby nobody can be down-tiered, and in a BR 1 lobby nobody can be up-tiered.

Your own BR is read from the loadout you spawned with, so picking a gun off a corpse — enemy or ally — cannot change it.
Why do I have two ratings?
Console players get one rating per ladder. The Main-ladder rating counts only your games with PC players in the lobby; the Console-ladder rating counts ALL your games (your mixed games still inform it — one-way). If your Main rating looks lower, it's because it only measures you against the PC player pool. Your player page shows both, and you can filter your match history to either set.

The technical version

Everything above, stated exactly: one master equation, the full pseudocode, the per-stat transforms and the complete 9×17 weight matrix.

The whole thing as one formula

Everything the engine does to your rating in a single match is this one update (each piece defined below):

μ' = max( 200,  μ + C10[ L[  (Q / (1/σ² + Q²go²ê(1−ê))) · go · ( (1−a)·(S* − ê) + a·(P − P̂) ) ] ] )

where
L = in a LOSS, a positive step is cut to 70%  — loss-gain cap, 2026-07-16
σ ≤ max(σmin, 600 / √games) when the step is taken  — sigma cap, 2026-10-06
ê = Λ( slopemap · Q · g · (μ̄you − μ̄them) + ctx )   — predicted win chance (the bar)
P = Λ( Σs∈17 stats W[mission:side][s] · zs / 1.8 ) · gate(record)   — your performance vs the lobby
P̂ = the P that players this far above or below the lobby's average rating usually score   — learned slowly from earlier matches (expected stats, 2026-10-05)
S* = result (1/0)
a = (0.7 if won, 0.6 if lost) · rampnew(games) · dampblowout(margin)   — how much the stat line counts (losses: less, since 2026-07-16)
C10 = clamp to ±75 during your first 10 games; Λ = logistic; Q = ln10/400

The full pseudocode

## CONSTANTS & PER-PLAYER STATE
Q          = ln(10)/400 = 0.005756       # classic Elo logit scale
μ          = mean of players with 20+ rated matches − 25, once 200 such players exist   # skill estimate at first sight (1000 while the field is small)
σ          = 377.19                        # uncertainty; floor 25.81, shrinks every game
games      = rated matches so far          # W/L/D rows only
record     = career wins/games             # never includes the current match
[AI]       = ONE shared rating for every bot

## STAGE 1 — BEFORE THE MATCH: predict P(team A wins) = E
# team skill: honest pre-match roster, softmax by μ with β=0.0007: your strongest players weigh a little more than the plain mean.
#   map-veto: drop a player in the battle under 60 s, the same line as a quit counting
#   (a bot: under 2% of the match): loaded in, disliked the
#   map/mode and left — never really on the team:
w_i    = exp(0.0007 × (μ_i − max μ on team))
teamμ  = Σ w_i μ_i / Σ w_i ;   teamσ² = Σ w_i² σ_i² / (Σ w_i)²
g      = 1 / √(1 + 3 (Q √(teamσ²_A + teamσ²_B) / π)²)

slope  = SLOPE[mode]                       # inv 3.45 ass 3.09 dst 2.57 cnf 3.30 dom 3.56 other 1.45
f_map  = shrunk(map skill-agreement, k=20, centered on mode)
slope  = slope × (1 + 0.25 × (f_map − 1))

ctx  = −0.0578 × (premade-frac diff) + 0.2482 × (biggest-party-share diff)
     + attacker offset: inv +0.047  ass +0.782  dst +0.540
     + −0.4 × (bot-count diff) + −0.60 × (console-frac diff)
     + 0.5 × shrunk side-bias(map, k=20)   # symmetric maps only
     + −1.0 × (tier̄_A − tier̄_B)          # tier = lobby BR − BR you brought, clamped to ±1

     + −0.45 × (new_A − new_B)             # new = Σ humans exp(−games / 10)

# new = a team's newcomer load: 1.0 for a first rated match, 0.37 at 10
#   games, 0.14 at 20, ~0 for a regular. A fresh rating says "average" but
#   first matches are won ~44% of the time; lowering the starting rating
#   only shifted the whole scale, so the correction is made HERE, in the
#   expectation. Same roster as team skill (map-veto tail dropped); bots
#   and incognito rows carry no load. Prediction only — no rating is
#   moved for being new or for playing beside someone who is.
#
# tier = (lobby BR) − (your own BR), clamped to one tier either way and
#   to the real BR scale (BR runs 1..5, so no "BR 0" and no "BR 6"):
#     tier = matchBR − clip(yourBR, max(1, matchBR−1), min(5, matchBR+1))
#   POSITIVE = up-tiered = placed above what you brought = bar drops.
#   It lands in {−1, 0, +1}: a placement flag, NOT a gear score. Your
#   own BR is read from the loadout you SPAWNED with, so a gun picked up
#   off any corpse cannot move it, and the enemy's gear never enters at
#   all — equipment does not rate you.
#   Needs ≥3 BR-known humans per team, else the term drops out.
#
# Weight 1.0: a team up-tiered by one whole bracket more than its opponents
# has its expectation lowered by about what a 170-Elo gap does at slope 1.
# The older lineup-BR term (team mean BR difference) is RETIRED: it let
# your own equipment move your rating, which this engine must not do.

E = logistic( slope × Q × g × (teamμ_A − teamμ_B) + ctx )

## STAGE 2 — AFTER THE MATCH: grade every human player
x[stat] = raw / minutes_played             # 17 counting stats per minute
# z-pools: captures/points/obj_kills_att pool ATTACKERS only, obj_kills_def DEFENDERS;
# deaths pool the whole lobby. Transform per stat (table below), then:
z[stat] = (transform(x) − lobby mean) / lobby stddev     # missing → 0; winsor caps ±2
z = Σ W[mission:side][stat] × z[stat]    # full 9×17 matrix below
perf = logistic(z / 1.8)
if record < 50% (after 10 games): perf ×= max(0, 1 − 0.5(0.5−record)/0.5)

S = 1 if won else 0
a = 0.7 if won else 0.6               # a lost match grades 60/40, not 70/30 (alpha_loss)
if WON a blowout: a ×= (1 − 0.7 × margin)     # coasting a stomp isn't punished
if games < 8:     a ×= 0.75 + 0.25 × games/8  # newcomers lean on the RESULT
target = (1−a)×S + a×perf
gap = your μ − mean μ of the humans in the match
expected = usual perf at this gap                # table of earlier matches, 100-point steps

## STAGE 3 — MOVE THE RATING (Glicko step, exact)
g_o   = 1 / √(1 + 3 (Q √(opponent teamσ²) / π)²)
e     = your team's E
par   = (1−a)×e + a×expected              # result judged against the win chance, stats against expected
σ     = min(σ, max(25.81, 600 / √games))   # uncertainty capped by matches played
d²    = 1 / (Q² g_o² max(e(1−e), 1e-6))
denom = 1/σ² + 1/d²
Δ = (Q / denom) × g_o × (target − par)    # scales with σ² when new
if LOST and Δ > 0: Δ ×= 0.7              # loss-gain cap — a gain in a loss keeps 70%
if games < 10: Δ = clamp(Δ, ±75)         # placement cap — no first-game jackpots
μ = max(200, μ + Δ)                        # hard floor
σ = max(25.81, √(1/denom))

## STAGE 4 — DESERTION
# matches from 2026-10-05 on:
left early, in the battle ≤ 60 s  → not rated (clock starts at your first spawn)
left early, in the battle > 60 s  → a LOSS with target = 0 (stats can't soften it)
# older matches: the line was 35% of the match instead of 60 s
# a quit costs once; it never changes how a later match is graded
every human on one team left (bots holding it) → match NOT RATED for anyone, any date

## STAGE 5 — WHAT THE LADDER SHOWS
Elo    = μ ± σ
Rating = 825 + (μ − 2σ − 825) × (1 − e^(−games/30))
         # experience shrink: 49% of your edge at 20 games, 81% at 50, 96% at 100
Tier   = live percentile of Rating (rated ≥ 10, recut daily):
         Diamond top 0.5% · Platinum 3% · Gold 12% · Silver 40% · Bronze rest

Per-stat transforms

Each stat is reshaped before it's z-scored, so long-tailed counts don't swamp the grade. Grouped by the transform applied:

transformapplied towhat it does
sqrtkills, building_usage, obj_kills_att, long_range_kills, kills_as_infcompresses big numbers — a 40-kill game isn't 4× a 10-kill game
log1pdeaths, obj_kills_def, fortification_builtstrong compression for counts with long tails; log(1+x) so 0 stays 0
ranksquad_deaths, vehicle_kills, rally_usage, kills_as_vehreplaced by lobby rank — only the ordering matters, not the raw gap
winsor ±2assists, headshots, points_capturedkept linear but clipped at ±2σ so one outlier can't dominate
linearcaptures_credited, battle_scoreused as-is (after per-minute), then z-scored like everything else

The full weight matrix W

Your job that match picks the column: inv=invasion, ass=assault, dst=destruction, cnf=confrontation, dom=domination; att/def=side, sym=symmetric. Green = raises your grade (deeper = stronger); red = lowers it. A dash (—) means the stat isn’t scored for that side — capture stats only count for attackers, defend-kills only for defenders — so its trained weight there never touches the grade. Death penalties on the three DEFENDER columns are zeroed. Defenders have had a ticket pool since 29 September 2026, but a re-fit on the matches after that date still found the penalties made predictions worse, so assault is graded the same way before and after the update.

weight strength: negative~00.30–0.800.80–1.201.20+— not scored for this side
statinv:attinv:defass:attass:defdst:attdst:defcnf:symdom:symother
kills1.371.421.460.900.150.991.831.060.88
deaths−0.480−0.920−0.600−0.27−1.490
assists1.041.811.290.530.311.440.140.230.29
captures_credited0.63—0.40—0.66—1.560.991.74
squad_deaths−1.100−0.820−0.240−1.47−0.21−1.82
vehicle_kills0.461.070.830.360.490.520.9100.71
building_usage0.460.330.440.170.880.590.300.601.44
battle_score0.340.610.060.250.880.860.611.491.04
obj_kills_att0.54—0.39—0.92—0.541.070.21
obj_kills_def—0—0.62—0.460.880.620.59
headshots0.070.930.590.490.250.721.131.140.37
points_captured0.49—1.13—1.08—0.191.820.49
fortification_built0.1800.450.5400.891.240.130.38
long_range_kills0.530.030.650.890.760.700.351.230.15
rally_usage1.320.180.830.071.810.330.040.471.05
kills_as_inf1.45000.540.200.840.541.180.78
kills_as_veh0.350.410.210.400.270.301.141.291.06

Not scored at all (weight 0 in every column): kd, human_kills, killstreak. They mostly repeat what the stats above already measure, and leaving them out made predictions more accurate.

Everyone is re-rated from scratch, oldest match first, whenever the formula changes — the ladder is always one consistent formula end to end.