Rainbow Six Siege ranks stopped meaning what they used to on June 2, 2026. That’s when Ubisoft shipped Ranked 3.0 alongside Operation System Override, stretching the ladder to 40 ranks and giving every tier, including Champion, a full five divisions. If you climbed under the old system and came back to find your rank card looks unfamiliar, you’re not imagining it. This guide walks through the current rank structure, how Ranked Points (RP) and hidden MMR actually interact, and how to build a real tracking setup so you know exactly where you stand instead of guessing from a colored icon.

We’ll cover the full Copper-to-Champion ladder, the eligibility checks Ubisoft runs before you queue, how to pull and log your own rank data, and the connection fixes that stop disconnects from tanking your RP. By the end you’ll have a working Python tracker that logs every ranked match and charts your season progress, plus a troubleshooting list for the most common ranked headaches players report in 2026.

None of this requires a paid tool or a browser extension. Everything here runs from a terminal and a text editor, which means the tracker keeps working even if a third-party stats site changes its layout or goes down for maintenance mid-season. That matters more than it sounds like it should. Community trackers have gone dark for days at a time in past seasons right when Ubisoft pushed a balance patch, which is exactly when players want to see how a rank reset or a new operator shook up their climb.

Prerequisites: What You Need Before You Start

Gather these before working through the steps below:

  • Rainbow Six Siege X installed via Ubisoft Connect, Steam, or your console’s store, patched to the Operation System Override build (live since June 2, 2026)
  • A Ubisoft account that has cleared the game’s ranked eligibility checks (minimum account level and onboarding matches, verified automatically when you open the ranked queue)
  • Python 3.10 or newer, if you want to build the RP tracker in the later steps
  • The pandas and matplotlib Python packages (install with pip install pandas matplotlib) for the logging and charting scripts
  • Administrator or terminal access on your PC for the network troubleshooting commands
  • About 30 minutes for the setup steps, plus ongoing time each session to log matches

Step 1: Learn the Full Rank Ladder, Copper to Champion

Before you can track progress, you need the full picture of what you’re climbing toward. Ranked 3.0 uses eight tiers, each broken into five divisions numbered V (lowest) through I (highest). That’s a jump from the earlier Ranked 2.0 ladder, which ran 36 ranks total because Platinum and Emerald only had three divisions each and Champion had none. Under the current system every tier, Champion included, carries the same five-division structure, for 40 ranks in total.

TierDivisionsWhere it sits on the ladder
CopperV – IEntry tier, first ranked placements land here
BronzeV – IThe most densely populated tier on the ladder
SilverV – IMid-ladder, win rate starts mattering more
GoldV – IUpper-mid, coordinated play becomes the norm
PlatinumV – IConsistent utility usage and callouts expected
EmeraldV – IAdded in Ranked 2.0 to smooth the jump into high ranks
DiamondV – ITop few percent of the ranked population
ChampionV – INow split into five divisions, previously a single rank

Ubisoft added Emerald during the Y7S4 Ranked 2.0 update specifically to soften what had been a steep jump between the middle of the ladder and the top. That design goal carried into Ranked 3.0’s expanded division count, so treat Emerald as a genuine high-skill tier rather than just another rung above Platinum.

Within a tier, moving from division V to division I follows the same pattern each time: earn enough RP and you promote, drop below the floor and you demote, with the game showing a short buffer near each boundary so a single unlucky match right at a promotion threshold doesn’t immediately bounce you back down. Don’t rely on that buffer as a strategy, though. It’s a smoothing mechanism, not a safety net, and it disappears once you’re clearly settled into a new division.

How Ranked 3.0 Differs From Ranked 2.0

If you’re coming back to Siege after a break, it helps to see the two systems side by side rather than trying to piece it together from patch notes. The table below covers the structural changes that matter most for how you’ll approach climbing.

AspectRanked 2.0 (pre-June 2026)Ranked 3.0 (current)
Total ranks3640
Champion divisionsNone, single rankFive divisions (V-I)
Platinum and Emerald divisionsThree eachFive each
Placement matchesRemoved, persistent hidden MMRRemoved, persistent hidden MMR
Squad MMR restrictionRemoved (1,000 MMR cap lifted)Still removed
Rank-determining metricRP, not raw MMRRP, not raw MMR

The headline change is division granularity, not a philosophy shift. Ubisoft didn’t touch how RP or hidden MMR work at a fundamental level between the two systems, it just gave players more visible checkpoints on the way up. That’s good news if you’re tracking your own progress: the underlying math from Step 6 onward still applies whether you started your season under the old ladder or the new one.

Step 2: Understand RP vs. Hidden MMR

The rank icon on your profile is driven by Ranked Points, not your raw matchmaking rating. Ubisoft’s Ranked 2.0 update moved the visible rank away from directly reflecting MMR. Instead, you earn or lose RP after each match, and fixed RP thresholds separate each division. Your hidden MMR still exists behind the scenes and it’s what matchmaking actually uses to build lobbies, but it no longer resets your visible rank at the start of a season.

That distinction matters for a tracker. If you only log your visible rank, you’ll miss why some wins earn more RP than others: a win against a lobby your hidden MMR rates as tougher pays out more RP than a win against a lower-rated lobby, even if both wins land you in the same tier and division. Log the RP delta per match, not just the rank name, and the pattern becomes visible after a few sessions.

Picture two players sitting in Gold II. Player A wins five matches against lobbies the matchmaker rates close to their own MMR and gains a steady 20 to 25 RP per win. Player B wins five matches against noticeably weaker lobbies, maybe because a full squad queued down with a lower-rated friend, and gains only 8 to 12 RP per win despite the same five wins. Both players see “5-0” in their session summary, but their RP trend lines look completely different. That gap is the hidden MMR system doing its job, and it’s exactly the kind of thing a raw win-loss count hides from you.

Step 3: Confirm You’re Ranked-Eligible

Open the ranked tab before you queue and check for any eligibility warnings. Ubisoft runs an automatic check against your account level and match history, and it will block ranked queue access with an on-screen message if you haven’t met the requirement yet. New or returning accounts sometimes hit this wall unexpectedly after long breaks, so don’t assume access carries over automatically between seasons.

One change worth knowing from Ranked 2.0 onward: Ubisoft removed the old 1,000-MMR squad restriction, so you can now party up with friends regardless of the skill gap between your accounts. That’s a real quality-of-life fix if your squad spans a wide range of ranks, but it also means lobbies can feel less predictable when a high-MMR friend queues with a lower-ranked one.

If you’re setting this guide up on a new account or a smurf, budget extra time for the eligibility check specifically. The onboarding requirement exists to keep brand-new accounts out of ranked lobbies where they’d be mismatched against experienced players, and Ubisoft enforces it client-side before the queue button even becomes clickable. Trying to skip ahead by editing local save data or using third-party rank boosters violates the terms of service and risks a ban, so the only reliable path is playing the required matches normally.

Step 4: Check Your Current Rank In-Game

Your rank card lives on the main menu and inside the ranked queue screen. It shows your current tier, division, and RP progress toward the next division. Click into the ranked stats panel for a season summary: wins, losses, abandons, and your RP trend line since the season began. Screenshot or note this number before your first tracked session, since it becomes your baseline for the logging steps below.

Console players can find the same panel under their platform’s in-game stats menu, though the layout differs slightly from the PC client. Whichever platform you’re on, write down your starting tier, division, and RP total before moving to Step 5.

Step 5: Pull Your Rank Data Into a Trackable Format

Third-party stats trackers pull post-match data and display it in a browser dashboard, which is useful for a quick look but painful for spotting long-term trends across a full season. The fix is to record your own numbers locally after each session, in a format you control. Start with a simple check that your tracking environment is ready:

python3 --version
pip install pandas matplotlib
python3 -c "import pandas, matplotlib; print('tracker environment ready')"

If that last line prints without an error, you’re set up to build the logger in Step 9. This local-first approach also sidesteps a real problem with browser trackers: a site outage or a layout change doesn’t erase weeks of data you’ve already recorded yourself.

Step 6: Calculate the RP You Need to Rank Up

Ubisoft hasn’t published an official, fixed RP-per-division table for Ranked 3.0, and the exact number can shift by season, so don’t hardcode a value you found in a forum post. Instead, pull the RP-to-next-division figure straight from your own rank card (it’s displayed right on the panel from Step 4) and feed it into a small calculator. This keeps the math accurate to your actual account instead of a number that might be outdated by the time you read it.

# rp_calculator.py
# Fill in the two values from your in-game rank card, then run this script.

rp_needed_for_next_division = 220   # shown on your rank card
average_rp_per_win = 28             # your recent average, from Step 9's log
average_matches_per_session = 6

matches_needed = -(-rp_needed_for_next_division // average_rp_per_win)  # round up
sessions_needed = -(-matches_needed // average_matches_per_session)

print(f"Wins needed at current pace: {matches_needed}")
print(f"Sessions needed at {average_matches_per_session} matches each: {sessions_needed}")

Update average_rp_per_win weekly once you’ve got real data from your log. Early estimates will be rough, but the number tightens up fast once you’ve logged 15 to 20 matches.

Step 7: Queue Smart Now That Squad MMR Limits Are Gone

With the old MMR party cap removed, you’ll see wider skill spreads in your own lobbies when you duo or five-stack with friends of different ranks. That’s not automatically bad, but it does change how you should interpret a loss. If you queue with a squadmate two tiers below you and drop a match, don’t read that purely as your own RP dropping from personal underperformance. The matchmaker is balancing around your squad’s combined MMR, which pulls lobby difficulty in a direction that doesn’t match your solo skill level.

A practical habit: tag each logged match with whether you queued solo or in a party, and note the party’s rank spread. After a few weeks you’ll be able to see whether wide-spread parties are actually costing you RP pace compared to solo queue, instead of guessing.

This is also where communication habits matter more than most players expect. A five-stack with a wide skill spread only outperforms solo queue when the higher-ranked players actually call out information the lower-ranked ones would miss, like reading drone footage out loud or flagging a rotate before it happens. If your squad plays a wide-spread party the same way you’d play solo queue, silently and reactively, you’ll likely see worse RP pace than solo queue would give you, simply because the matchmaker is pricing in coordination that isn’t showing up on the server.

Step 8: Test and Fix Your Connection Before Ranked Queues

Disconnects and packet loss cost more than a single match. A mid-match drop can register as an abandon, which carries a heavier RP penalty than a clean loss. Run a quick connection check before you start a ranked session, especially after a router restart or an ISP outage in your area.

# Windows PowerShell - run as your normal user
Test-Connection -ComputerName www.ubisoft.com -Count 10

# If you're seeing timeouts or high latency spikes, reset local network state:
ipconfig /flushdns
netsh winsock reset
netsh int ip reset

The winsock and IP resets require a restart to take effect, so run them between sessions rather than mid-queue. On macOS or Linux, ping www.ubisoft.com and a router restart cover the same ground for a quick pre-session check.

Step 9: Log Every Match So You Can See Your Real Trend

This is the core of the tracker. Rather than relying on memory or a screenshot folder, append one row per match to a CSV file right after it ends. It takes 15 seconds and it’s the data that everything else in this guide runs on.

# match_logger.py
import csv
from pathlib import Path

LOG_FILE = Path("ranked_log.csv")

def log_match(date, result, rp_change, tier, division, queue_type):
    is_new_file = not LOG_FILE.exists()
    with LOG_FILE.open("a", newline="") as f:
        writer = csv.writer(f)
        if is_new_file:
            writer.writerow(["date", "result", "rp_change", "tier", "division", "queue_type"])
        writer.writerow([date, result, rp_change, tier, division, queue_type])

# Example call after a match:
log_match("2026-08-15", "win", 31, "Platinum", "III", "solo")

Run this once per match with your real numbers swapped in, or wrap it in a tiny prompt loop if you’d rather type values at a terminal than edit the script each time. Either way, after two or three sessions you’ll have enough rows to make Step 6’s calculator genuinely useful instead of a guess.

Step 10: Read the Rank Distribution Data to Set a Real Goal

Knowing where a rank sits on the population curve makes your goal concrete instead of abstract. Ubisoft hasn’t published a settled, official distribution table for the 40-rank Ranked 3.0 ladder yet, since the system only launched in June 2026 and trackers are still recalibrating their samples. The most recent official-sourced snapshot comes from before the expansion, based on November 2025 PC data, and it still gives a useful sense of scale for how rare the top tiers are.

TierShare of ranked playersPercentile
Bronze IV (most populated single rank)~7.77%Broad mid-ladder mass
Bronze V~7.69%Broad mid-ladder mass
Emerald (all divisions combined)~5.5%Top ~8.6%
Diamond (all divisions combined)~2.7%Top ~3.1%
Champion~0.2%Roughly 500-600 accounts in the tracked sample

One quirk worth flagging: a separate sample restricted to players with 100 or more matches in a season showed Emerald jumping to 16.3% of that active subset, nearly three times its share of the broad population. That gap tells you something useful: Emerald isn’t rare because it’s unreachable, it’s rare because most of the player base doesn’t put in enough matches to get there. Grinding consistently moves you into a very different comparison pool than the full playerbase average.

Use this when you set a season goal. If your target is Emerald and you’re realistically going to play 40 to 60 ranked matches over a season rather than 150-plus, compare yourself against the broad-population numbers, not the active-grinder subset. Chasing a target calibrated to a 100-plus-match sample when you can only commit to half that volume sets you up to feel like you’re underperforming when you’re actually on a normal pace for your available time.

Step 11: Avoid Inactivity Decay

Long breaks from ranked queue can affect your standing, particularly at the higher tiers where the system expects continued activity to validate your rank. If you’re planning a multi-week break mid-season, check the in-game ranked panel for any decay warning before you stop playing. The safest move is to play at least a handful of ranked matches on a regular cadence rather than binge-queuing for one weekend and going silent for a month.

Your logged CSV from Step 9 doubles as a decay early-warning system too. If you see a string of matches with unusually large RP losses after a gap, that’s worth cross-checking against the in-game panel rather than assuming it’s just matchmaking variance.

Step 12: Build a Repeatable Climbing Routine

Consistency beats streaks. A player who logs five focused ranked matches three times a week tends to climb more predictably than one who plays fifteen matches in a single burnt-out session on Saturday. Pick a fixed operator pool for your rank range, warm up in a quick match or two before queuing ranked, and stop for the day after two losses in a row rather than tilt-queuing a third.

Review your CSV log weekly. Look specifically at RP change by queue type (solo vs. party) and by day of week. Most players find a pattern, like a noticeably worse win rate on weekend-night queues when lobbies skew toward off-hours players, and that pattern is only visible once you’ve got two or three weeks of rows to compare.

How Season Resets Affect Your Rank

Since Ranked 2.0 removed placement matches, a new season doesn’t wipe your standing back to zero the way older Siege seasons did. Your hidden MMR persists between seasons, so when a new season opens you’re placed based on that carried-over skill data rather than grinding through a fresh set of ten placement games. In practice this means your first few matches of a new season tend to land you close to where you finished the previous one, adjusted slightly for a soft reset Ubisoft applies to keep the top of the ladder from becoming permanently locked.

That soft reset is worth planning around if you’re tracking a full-season goal. Log the date of each season boundary in your CSV, either as a note field or by starting a new file per season, so your RP-per-match average from Step 6 doesn’t get thrown off by a reset-related dip in the first week. A drop right after a season starts is expected behavior, not a sign your pace has actually slowed.

Cosmetic season rewards and rank-based unlocks are usually tied to your highest rank achieved during the season, not just your rank at the final match, so a strong mid-season peak still counts even if a late slump pulls your visible rank down before the season closes. Check the specific season’s reward terms in-game, since the exact wording can shift from one operation to the next.

Complete Project: A Season RP Tracker Dashboard

Put the pieces from Steps 6, 9, and 10 together into one finished tool. This last script reads your ranked_log.csv file and plots RP over time, so you can see your season trend at a glance instead of scrolling through rows of numbers.

# season_dashboard.py
import pandas as pd
import matplotlib.pyplot as plt

df = pd.read_csv("ranked_log.csv")
df["date"] = pd.to_datetime(df["date"])
df = df.sort_values("date")
df["cumulative_rp"] = df["rp_change"].cumsum()

win_rate = (df["result"] == "win").mean() * 100
avg_rp_per_match = df["rp_change"].mean()

print(f"Matches logged: {len(df)}")
print(f"Win rate: {win_rate:.1f}%")
print(f"Average RP per match: {avg_rp_per_match:.1f}")

plt.figure(figsize=(10, 5))
plt.plot(df["date"], df["cumulative_rp"], marker="o")
plt.title("Season RP Progress")
plt.xlabel("Date")
plt.ylabel("Cumulative RP change")
plt.tight_layout()
plt.savefig("season_progress.png")
print("Chart saved to season_progress.png")

Run this after every few sessions. The printed win rate and average RP per match feed straight back into Step 6’s calculator, so the whole system becomes self-correcting: log matches, recalculate your pace, adjust your routine, repeat. That loop is worth more over a full season than any single climbing tip.

Once the base version is working, it’s easy to extend. Add a column for the map played and group your rp_change average by map to surface the weak spots mentioned in the advanced tips section below. Add a column for operator picks and you can spot whether a particular loadout is quietly underperforming across your sessions. None of these extensions require new libraries, just additional columns in the same CSV and a couple more lines of pandas grouping code.

Common Pitfalls When Climbing Ranked

  • Hardcoding RP thresholds you found online. Ubisoft hasn’t published a fixed, official per-division RP table for Ranked 3.0, and community numbers drift by season. Pull the figure from your own rank card each time instead.
  • Confusing visible rank with hidden MMR. Your matchmaking lobbies are built from hidden MMR, not your rank icon. A high-RP win against a weaker lobby won’t pay out like a win against a lobby your true MMR rates as tough.
  • Queuing wide-spread parties and blaming yourself for losses. Since the squad MMR restriction was removed, uneven-rank parties can pull lobby difficulty in directions that don’t reflect your solo skill. Tag party matches separately in your log.
  • Playing through bad connection instead of fixing it first. An abandon from a mid-match disconnect costs more RP than a clean loss. Run the Step 8 connection check before, not during, a ranked session.
  • Comparing yourself to the wrong distribution sample. Broad playerbase percentages and active-grinder percentages tell very different stories, as the Emerald gap in Step 10 shows. Know which sample you’re reading before you judge your own progress against it.
  • Letting a long break run past the decay warning. Check the in-game ranked panel before stepping away for weeks at a time, especially at Emerald and above.
  • Treating a single bad session as proof the system is broken. One rough night of losses usually reflects fatigue, an off-meta operator pick, or just matchmaking variance, not a flawed rank system. Wait for a full week of logged data before drawing conclusions.
  • Deleting your CSV log to “start fresh” mid-season. Trends only become visible with enough rows. Starting over erases the exact history you’d need to spot a slump or a hot streak. Archive old data in a second file instead of deleting it.

Troubleshooting

Working issues you’ll likely hit while setting up or running this tracker, and what fixes each one.

  • Ranked queue is greyed out. Check the eligibility panel from Step 3. Recently created or long-dormant accounts sometimes need to clear an onboarding match count first.
  • RP gain seems inconsistent between wins. This is expected. RP payout scales with the strength of the opposing lobby relative to your hidden MMR, not a flat per-win amount.
  • ModuleNotFoundError: No module named 'pandas' when running the scripts. Your pip install didn’t target the Python interpreter you’re running. Try python3 -m pip install pandas matplotlib instead.
  • CSV file has duplicate header rows. This happens if LOG_FILE.exists() returns false because you’re running the script from a different working directory each time. Use an absolute path for LOG_FILE.
  • Chart script runs but no window opens. That’s normal on headless setups. The script saves to season_progress.png in the working directory rather than opening a window.
  • High ping only during ranked queue, not in menus. This usually points to regional server load rather than your own connection. Try queuing at a different time of day before assuming it’s a local network issue.
  • Frequent disconnects after a router restart. Run the winsock and IP reset commands from Step 8, then restart your PC. A partial network stack reset without a restart often doesn’t fully apply.
  • Rank card shows a different RP-to-next-division number than yesterday. This can shift slightly between matches based on your hidden MMR movement. Re-check the number each session rather than assuming it’s fixed for the whole season.
  • Tracker CSV shows a match with no RP change at all. That’s typically a match that ended in a draw or was voided by the server, not a logging error. Note it separately rather than deleting the row.
  • Script throws a KeyError on the “date” column. This usually means a header row got skipped or duplicated earlier in the file. Open the CSV in a spreadsheet app and confirm there’s exactly one header row at the top before rerunning the dashboard script.
  • Matplotlib chart looks empty or shows a flat line. Double-check that rp_change values are being logged as numbers, not text. A stray quote mark around a number in the CSV will make pandas treat the whole column as strings, which breaks the cumulative sum.

Advanced Tips for Breaking Into Emerald and Above

Once your logging routine is solid, a few habits separate players who stall out at Platinum from those who push into Emerald and beyond. First, narrow your operator pool hard once you’re in the top half of the ladder. Lobbies get more coordinated fast, and split attention across a wide roster costs more at this level than it did in Bronze or Silver.

Second, use your CSV log to separate map-specific win rates from your overall average. Most players have two or three maps that quietly drag their season average down. Banning or avoiding those in ranked, where the client allows it, protects your RP pace more reliably than grinding harder on maps you’re already weak on.

Third, treat the active-player distribution gap from Step 10 as a planning tool. If Emerald holds roughly three times the share among 100-plus-match grinders that it does in the broad population, then match volume itself is part of the climb, not just mechanical skill. Budget for it. A realistic season goal accounts for the number of matches you can actually put in, not just the win rate you’d need in an ideal world.

Finally, revisit Step 8’s connection check weekly, not just once. ISP routing changes and regional server load shift over a season, and a setup that ran clean in June can develop new latency spikes by August.

One more habit worth building: review replays of your losses, not your wins. It’s a cliché piece of advice, but the CSV log makes it actionable instead of vague. Cross-reference your three or four worst RP-loss matches from the past two weeks against the replay system and look specifically for the moment the round tipped, not just the final kill feed. Most players find the same mistake repeating across losses (over-peeking a common angle, rotating too late after a plant) once they look at three or four replays back to back instead of one in isolation.

If you’re playing on console, the connection troubleshooting from Step 8 still applies conceptually even though the exact commands differ. Check your console’s network settings menu for packet loss or NAT type warnings, and prioritize a wired connection over Wi-Fi during ranked sessions if your setup allows it. NAT type issues in particular can cause the exact kind of mid-match instability that turns a winnable round into an abandon.

Frequently Asked Questions

How many ranks are in Rainbow Six Siege as of 2026?
Forty. Ranked 3.0, live since June 2, 2026, uses eight tiers (Copper, Bronze, Silver, Gold, Platinum, Emerald, Diamond, Champion), each split into five divisions numbered V through I.

What’s the difference between RP and MMR in Rainbow Six Siege?
RP (Ranked Points) is the visible number that determines your tier and division. MMR is a hidden rating the matchmaker uses to build lobbies. They’re related but not identical, which is why RP payouts vary between wins.

Do placement matches still exist?
No. Ubisoft removed placement matches starting with Ranked 2.0. Your hidden MMR carries over between seasons instead of resetting, so you’re placed based on persistent skill data rather than a fresh set of placement games.

Can I still queue ranked with friends of very different skill levels?
Yes. The old 1,000-MMR squad restriction was removed in Ranked 2.0, so parties can now span a much wider rank range than before.

How rare is Champion rank?
Very. In the most recent official-sourced snapshot, Champion accounted for roughly 0.2% of the ranked player base, on the order of 500 to 600 accounts in the tracked PC sample.

Why did my RP drop even though I won the match?
This shouldn’t happen on a standard win, but abandons, voided matches, or connection drops mid-match can register differently than a clean win. Check your match history for an abandon flag if you see an unexpected RP loss.

Is there an official Rainbow Six Siege rank distribution for Ranked 3.0 yet?
Not as a settled, official table. The system launched in June 2026, and as of this guide’s publication Ubisoft hasn’t released a full post-expansion breakdown, so community trackers are still building fresh samples.

Does rank decay if I stop playing for a few weeks?
Extended inactivity can affect your standing, especially in the higher tiers. Check the in-game ranked panel for a decay warning before taking a long break.

What happened to Platinum and Emerald only having three divisions?
That was a feature of the earlier Ranked 2.0 ladder. Ranked 3.0, live since June 2, 2026, gave every tier, Platinum and Emerald included, the full five-division structure that Copper through Gold already had.

Do I need a paid stats tracker to follow this guide?
No. Every script in this guide runs locally with free, open-source Python packages. A browser-based tracker can be a useful supplement, but nothing here depends on one.

Sources: Ubisoft’s Ranked 2.0 update notes, Ubisoft’s Ranked 2.0 findings post, Siege.gg’s Emerald rank coverage, Esports Tales’ seasonal rank distribution data, and HotSpawn’s Rainbow Six Siege X ranks guide.