๐Ÿ“Š

Understanding Stat Estimates

TORN CITY // GUIDE

Guide ยท FF, spy, verified & rank estimation

Why you can't just look up someone's stats

A player's battle stats โ€” strength, speed, dexterity, and defense โ€” are private by default. Torn only shows you your own numbers. Every "how strong is this person" question in the game is really a question of estimation: piecing together indirect signals into a best guess, and knowing how much to trust that guess.

Fair Fight (FF) leakage

Torn's Fair Fight mechanic scales the respect and rewards from a hit up or down depending on how your total stats compare to your opponent's. Because that multiplier is visible after a fight, and it moves in a predictable curve relative to the stat gap between the two fighters, it's possible to work backwards from a series of fights to a rough estimate of the opponent's total stats. This is the basis of FF estimation โ€” the same approach tools like FFScouter are built on: it doesn't require the opponent's cooperation, but it's only as good as the number and spread of fights available to learn from, and it degrades if a player has trained heavily since the last observed fight.

Spy reports

Certain company perks let specific job roles attempt to spy on a target's battle stats โ€” a single attempt can reveal the full breakdown or only part of it, and a stronger target typically takes more attempts before the picture is complete. Third-party sites also aggregate spy results members choose to share. When available, a spy report is the most precise non-verified source โ€” but it's a snapshot: accurate the moment it's taken, and steadily less reliable as time passes and the player keeps training.

Verified totals

Some players choose to make their total battle stats visible directly โ€” for example, by connecting an API key with battlestats access to a tool they trust, which reads their real total straight from Torn rather than inferring it. A verified total is the ground truth: it isn't an estimate at all, it's the actual number, current as of when it was read. It's the highest-confidence source available, but it only exists for players who've opted in to share it.

Rank brackets

When none of the above are available, the fallback is a player's rank โ€” the broad tier Torn assigns based on stats and activity. Rank brackets are wide, so this is the lowest-confidence estimate: useful for a rough "is this person plausible to fight" sanity check, not for close calls.

Combining sources: best-available estimation

None of these sources is available for every player, and they don't agree in precision, so a useful tool has to pick the best one it has for each individual and be honest about which it used. A sane priority order is: verified total (ground truth) > spy report (precise, ages quickly) > FF estimate (indirect, needs enough fight data) > rank bracket (coarse, always available as a fallback). Labelling every number with its source and how recently it was captured matters more than the estimate itself โ€” the source tells you how it was derived, and the age tells you how much to trust it right now, which together do the same job as a separate "confidence" tag without needing one.

Why estimates need to be refreshed

Every active player is training, which means every estimate has a shelf life. A verified total from three months ago, or an FF estimate built from fights before a big stat-training push, can be badly out of date even though the number itself hasn't changed. Estimation is an ongoing process, not a one-time lookup โ€” the more recent fight data and verification signals a tool can draw on, the sharper (and more honest) its estimates stay.

โ–ถ See source & age-labelled estimates (demo)