Apex Seasons

Team Comp Builder

Build a trio with intent: class coverage, active perks, and synergy checks for more consistent ranked sessions.

Last verified: Season 28 — Feb 2026

Player 1
Player 2
Player 3
Browse All 26 Legends

How This Tool Works

The builder is for squad planning with intent: lock three legends, then review class balance, active perks, and known synergy pairs.

Coverage is the core idea. Multi-class squads usually keep more rotate, info, and reset options than triple-stack same-role comps.

Use random squad mode for practice blocks, then lock a stable trio when you are pushing ranked consistency.

Formula & Assumptions

  • Class balance is derived from selected legends only.
  • Active perks are aggregated from unique classes present in the squad.
  • Synergies are curated editorial mappings, triggered when required legend pairs are both selected.
  • Diversity indicator rewards multi-class compositions.

Example Scenario

  1. Start with Bloodhound, Bangalore, and Lifeline to blend recon, assault pressure, and sustain.
  2. Review active perks and synergy callouts to see what utility is missing.
  3. Swap one legend to test alternate playstyles for edge-fight versus zone-heavy matches.

Common Mistakes

  • Prioritizing comfort picks only and ending up with no beacon or support utility.
  • Over-trusting synergies without considering your team’s communication level.
  • Ignoring map or lobby style when selecting a comp.

Data Source & Update Policy

  • Legend roster and class definitions should be updated each season as new legends launch or class assignments change.
  • Synergy notes are explicitly community/editorial guidance and not official balance statements.
  • The tool favors transparent rule-based output over black-box recommendations.

How To Validate Any Output

Treat this page as a decision aid, not a black box. Start by checking that your inputs reflect your real situation (current rank, level, inventory, or playtime). Then compare one result against a real in-game outcome or official patch-note value. If the output is directionally right and assumptions match your case, use it for planning. If your local conditions differ, adjust assumptions and run another scenario before acting on the number.

The goal is transparent utility. Every calculator here intentionally exposes assumptions so you can audit the logic quickly and avoid common mistakes from outdated guides. That approach helps this site stay useful even when the Apex meta changes, because updating a few clearly documented values is faster and safer than rewriting hidden logic.