Why there is no official S/A/B/C table here
The supplied evidence includes the official Survivors Wiki for character facts and a Steam Community build discussion for player experience. Those sources are enough to describe kits and examples, but not enough to derive a complete, current, authoritative S/A/B/C ranking. Publishing one anyway would turn editorial confidence into fake data.
This page is still useful: it defines the comparison contract. A future placement should show the version, the run scope, the criteria, and the evidence behind each judgment. Until that work is done, use the dimensions below rather than a single letter.
Version, scope, and standards
Version boundary: the current 1.0 release context, with the Steam displayed date of 2026-08-20. Scope: solo runs with the mode and difficulty named in the test note. If a team comparison is made, record the full team and whether general points or special upgrades are allowed. A result without those controls should remain a lead rather than a tier placement.
The minimum standards are survival, clear coverage, boss or durable-target pressure, growth cost, and team compatibility. They are not all the same thing. A character can clear early waves while demanding a fragile route later, or have a slower opening but stronger compatibility once the team is established.
| Dimension | Question | Evidence needed |
|---|---|---|
| Survival | Can the route keep operating under pressure? | Repeat runs and failure point |
| Clear | Does it control enough of the active screen? | Mode, wave context, route notes |
| Boss pressure | Can it answer a durable target? | Target context, upgrade route, repeat test |
| Growth cost | How dependent is the result on rare offers? | Offer sequence and point context |
| Team fit | Does it cover or amplify a teammate job? | Full squad and synergy notes |
Evidence versus editor judgment
The Wiki can support statements about a character's ability, starting weapon, or documented unlock. The Steam discussion can support a statement that a player tried a route and reported an outcome. The placement itself is an editor judgment unless a broader, version-matched data set is available. Label each sentence accordingly.
A good comparison note might say: the Wiki documents the ability; a player discussion reports this route; in two stated tests, the editor observed a coverage gap. A bad note says a character is S tier because one post called it best. The first can be audited and updated; the second cannot.
How to build a future placement
Run at least a small repeatable set under the same scope, record the first failure and the upgrade dependencies, then publish a provisional comparison with the date. Do not hide uncertainty behind a letter. If the evidence is mixed, use a dimension-by-dimension note and leave the overall placement open.
The Characters index, Synergies, and weapon pages provide the supporting context. Tier List should point outward to those facts rather than duplicating every kit or pretending it has a separate database.
Reader takeaway
Use this page to compare a route honestly, not to outsource every decision to a letter grade. The strongest current conclusion is methodological: rankings need a version, a scope, explicit standards, and per-item evidence. Until those are assembled, no S/A/B/C verdict is claimed.