Jynxzi R6 Tracker: Track Your Rank in 12 Steps [2026]

Every few days, a new clip of Jynxzi grinding Rainbow Six Siege ranked lands on Twitch and the same question follows it into the search bar: what rank is Jynxzi in R6 right now? His stream titles over the past few weeks, “CHAMPION PUSH w STACK,” “CARRIED TO CHAMPION PC,” “SOLO TO CHAMPION PC,” all point the same direction, but his profile on R6 Tracker Network doesn’t return a clean answer. That gap between what viewers see on stream and what the public tools show is the real story here, and it’s also a useful excuse to learn how Rainbow Six Siege’s rank system actually works in late 2026.

This tutorial does two things. First, it walks through exactly how to check any player’s R6 Siege rank, your own or a streamer’s, using the tools that actually work under the game’s current Ranked 3.0 system. Second, it shows you how to build a small, self-hosted rank tracker in Python so you stop refreshing a tracker site every ten minutes during a push. By the end you’ll have a working script, a log of your RP history, and a clear answer for why some profiles, including high-profile streamers, simply don’t show up where you expect.

Rainbow Six Siege’s ranked ladder changed shape twice in 2026, and both changes happened while Jynxzi was actively streaming ranked pushes. Ranked 3.0 launched on June 2, 2026, as part of Year 11 Season 2, Operation System Override, and it tore out the hidden MMR system that had frustrated players since Ranked 2.0. In its place, Ubisoft made Rank Points, or RP, fully visible, so your number on screen is now the same number the matchmaker uses behind the scenes. Then, on October 15, 2026, barely a day before this article published, Ubisoft shipped a mid-season update called Operation Split Fire that added something new above the standard ladder: the Legend Division, a solo-queue-only playlist open to current Champions.

That timing matters for anyone trying to figure out Jynxzi’s rank. His September streams carried titles like “CARRIED TO CHAMPION PC” on September 14 and “SOLO TO CHAMPION PC” on September 26, both strong signals he was pushing toward or sitting in the Champion tier before Legend Division even existed. On September 12 alone, a Siege stream of his averaged 46,674 viewers with a peak of 197,241, and a 30-day TwitchTracker snapshot from late September put him at 36,874 average concurrent viewers across the Rainbow Six Siege category with 11.4 million hours watched in that window. Big audience, strong signal toward Champion, but no third-party site publishes a confirmed division or exact RP figure for him. That uncertainty is exactly why learning to read the ranked system yourself, rather than relying on a screenshot you saw on social media, is worth the fifteen minutes this guide takes.

Prerequisites: What You Need Before You Start

You don’t need to be a developer to complete the first half of this tutorial, checking a rank manually. The second half, building an automated tracker, needs a bit of setup. Here’s the full list before you begin.

A free Ubisoft Connect account linked to the platform you play Rainbow Six Siege on (PC, Xbox, or PlayStation)
Rainbow Six Siege installed, or at minimum a public profile set to visible stats, if you want in-game verification
A web browser to use R6 Tracker Network’s public lookup pages
Python 3.10 or newer installed on your machine (check with python3 --version)
The requests library, installed via pip (latest version)
Optionally, matplotlib (latest version) if you want to chart your RP history in Step 12
About 45 minutes if you’re doing every step, including the scripting portion

If you only want to answer “what’s my current rank” or “what rank is this streamer,” skip ahead to Steps 1 through 6. The scripting steps are for anyone who wants a standing record of their climb across a season.

Step 1: Learn the 40-Rank Ranked 3.0 Ladder

Before you can read anyone’s rank correctly, you need to know what the numbers mean. Ranked 3.0 uses eight tiers, Copper, Bronze, Silver, Gold, Platinum, Emerald, Diamond, and Champion, and each tier below Champion splits into five divisions, numbered V down to I, where I is the strongest division in that tier. That’s 40 individual ranks on the standard ladder. Champion itself doesn’t subdivide the same way; once you’re in, you’re ranked by raw RP against everyone else in Champion, and since October 15, 2026, the very top of that group can push into the new Legend Division, a separate solo-queue leaderboard sitting above Champion I.

RP moves roughly 80 points per win or loss, though the exact amount shifts based on your opponents’ average rank and your match performance, and divisions are spaced roughly 100 RP apart. That’s useful math: climbing a full division usually takes something close to two net wins, and climbing from the bottom of Silver to the bottom of Gold is a multi-session project, not an afternoon. Here’s the full tier breakdown.

Tier	Divisions	Approx. RP Range	Where Most Players Sit
Copper	V – I	0 – 499	New or returning accounts
Bronze	V – I	500 – 999	Casual ranked players
Silver	V – I	1000 – 1499	Large population band
Gold	V – I	1500 – 1999	Regular ranked grinders
Platinum	V – I	2000 – 2499	Mechanically solid players
Emerald	V – I	2500 – 2999	Competitive-minded squads
Diamond	V – I	3000 – 3499	Top percentile of the ladder
Champion	No sub-divisions	3500+	Includes the Legend Division leaderboard above Champion I

RP ranges above Silver shift slightly from season to season as Ubisoft tunes the curve, so treat these as the general shape of the ladder rather than a fixed cutoff you can set a watch by.

The Legend Division deserves a closer look since it’s brand new as of this week. Unlike the standard 40-rank ladder, it isn’t something you queue into directly from Copper. Access opens only once you’ve held Champion I, and the playlist itself is solo queue only, which Ubisoft framed as a way to rank individual mechanical skill separately from squad coordination at the very top of the ladder. Early community reaction has focused on how few players will realistically reach it in the first few weeks, since it stacks a second, harder gate on top of an already small Champion population. If a streamer’s title mentions “Legend push” rather than “Champion push” going forward, that’s the tell that they’ve cleared the first gate and are now grinding the second one.

Step 2: Create Your Ubisoft Connect and R6 Tracker Accounts

If you already play Rainbow Six Siege, you have a Ubisoft Connect account and you can skip to Step 3. If you’re setting this up fresh, head to Ubisoft’s account portal, create a free account, and link whichever platform you play on, PC through the Ubisoft Connect client, or your PlayStation Network or Xbox Live account on console. You don’t need to buy anything or install the game to look up a rank, since the lookup tools pull from your public match history, but you do need a valid, linked account if you want to check your own stats rather than someone else’s.

You do not need to create an account on R6 Tracker Network itself to search for a player. Its public leaderboard and profile search work without logging in. An account there only matters if you want to save favorite profiles or set up notifications on their end, which is a separate feature from what we’re building here.

Step 3: Find Any Player’s Profile on R6 Tracker Network

Open R6 Tracker Network’s leaderboard and search page and enter the exact in-game username, not a Twitch handle, since those are frequently different. This is the single most common mistake people make when they can’t find a streamer’s stats: searching “Jynxzi” when the player’s actual Ubisoft username is something else entirely, or vice versa. Platform matters too. If someone plays on PC through Ubisoft Connect, searching their name under an Xbox or PlayStation filter will return nothing, or worse, a different player who happens to share the name.

Once you’ve got the right username and platform combination, a correctly indexed profile shows current RP, rank tier and division, a season rank history chart, and a breakdown of operator and weapon stats. If the search comes back empty or shows “no stats found,” don’t assume the tool is broken, jump to Step 6, which covers exactly why that happens and what it usually means.

Step 4: Read RP, Division, and Season Data Correctly

A profile page can show a lot of numbers at once, and it’s easy to misread which one is current. Look specifically for a field labeled current season RP, which under Ranked 3.0 is the actual live number used for matchmaking, not an estimate. Separately, most trackers also show a peak RP for the season, which is the highest point a player reached before any losses pulled them back down. These two numbers tell very different stories: a player sitting at 3,420 current RP with a 3,610 peak has recently dropped a division, while a player whose current and peak match exactly is actively climbing or holding steady.

Also check the season label itself. Ranked 3.0’s season structure means RP resets, partially, at the start of each new season through placement matches, so a screenshot from Year 11 Season 2 tells you nothing reliable about someone’s rank in Season 3. If you’re trying to settle an argument about “what rank is this streamer right now,” confirm the season tag on the page matches the current one before you trust the number.

Step 5: Cross-Check With the In-Game Stats Menu

Third-party trackers are convenient, but they depend on Ubisoft’s data feed staying in sync, and occasionally there’s lag between a match ending and a tracker site updating. The most authoritative source for your own rank is always the Rainbow Six Siege client itself. Launch the game, open the Stats menu, and select the Ranked tab. This shows your live RP, current division, placement match progress if the season just started, and your win/loss record for the season without any third-party dependency.

If you’re trying to verify someone else’s rank rather than your own and they haven’t shared an in-game screenshot, the in-game menu obviously isn’t accessible to you, which pushes you back to the tracker sites and, realistically, to trusting whatever the player themselves has said on stream or social media. That’s the position most people checking Jynxzi’s rank are actually in: no public in-game access, an indexed tracker profile that doesn’t resolve cleanly, and stream titles as the closest thing to a primary source.

Step 6: Understand Why Jynxzi’s Rank Stays Hidden

There are three separate, perfectly ordinary reasons a prominent player’s stats won’t show up on a public tracker, and understanding them clears up a lot of confusion, not just about Jynxzi but about any streamer whose rank you’re trying to pin down.

Platform or username mismatch. A tracker search needs the exact Ubisoft username and the correct platform. A streamer’s displayed name on Twitch is frequently not their in-game ID, and some players swap platforms between console and PC.
Privacy settings. Ubisoft lets players set their stats to private, which blocks third-party trackers from pulling match data entirely, even though the player can still see their own numbers in-client. High-visibility streamers sometimes do this specifically to avoid being tracked or targeted by opponents who look up their rank before a match.
Indexing lag or account changes. Trackers index profiles based on recent match activity under a given account ID. If a player changed their username, switched accounts, or simply hasn’t had a tracker crawl their new matches yet, their profile can appear empty or outdated even though they’re actively playing.

Any one of these explains why searches for Jynxzi’s exact Champion division or current RP keep coming up short on public tools, even while his own stream titles make it obvious he’s deep into a Champion-tier push. The honest answer to “what rank is Jynxzi in R6” as of this writing is: very likely Champion, based on his own stream content, but not independently confirmed through a public tracker profile. That’s a more useful answer than a made-up number, and it’s also the right mindset to bring to any player you’re trying to look up who isn’t showing clean data.

Step 7: Set Up Python for Automated Rank Pulls

Checking your own rank by hand every day works fine, but if you’re grinding toward Champion across a long weekend, a small script that logs your RP automatically saves a lot of manual refreshing. Start by confirming Python is installed and creating a project folder.

mkdir r6-rank-tracker
cd r6-rank-tracker
python3 -m venv venv
source venv/bin/activate   # on Windows: venv\Scripts\activate
pip install requests

That gives you an isolated environment with the one required dependency, requests, for making HTTP calls. If you plan to chart your RP history later in Step 12, install matplotlib in the same environment now so you’re not switching contexts mid-project.

Step 8: Write Your Rank-Fetching Script

Public tracker sites change their page layout periodically, and most don’t publish a stable, documented public API with an access key, so the most durable approach for a personal script is to fetch the profile page’s text and search it for the pattern a rank badge reliably produces: one of the eight known tier names sitting next to a number. This is more resilient than hard-coding a CSS class that might get renamed in the next site redesign.

import re
import requests

TIERS = ["Copper", "Bronze", "Silver", "Gold", "Platinum",
         "Emerald", "Diamond", "Champion"]

HEADERS = {
    "User-Agent": "Mozilla/5.0 (personal rank tracker; contact: [email protected])"
}

def fetch_profile_html(profile_url: str) -> str:
    response = requests.get(profile_url, headers=HEADERS, timeout=15)
    response.raise_for_status()
    return response.text

def extract_rank(html: str):
    pattern = r"(" + "|".join(TIERS) + r")\s*(?:[IVX]{1,3})?\s*[-,:]?\s*(\d{3,5})\s*RP"
    match = re.search(pattern, html, re.IGNORECASE)
    if not match:
        return None
    tier, rp = match.group(1), int(match.group(2))
    return {"tier": tier.title(), "rp": rp}

Replace profile_url with the exact profile page you’d normally visit by hand after Step 3. Note the honest, descriptive User-Agent string: identifying your script clearly and keeping request frequency low is basic courtesy toward a site that’s giving you data for free, and it also makes your traffic easier for the site operator to distinguish from abusive scraping if they ever need to.

Step 9: Parse RP and Division From the Response

With extract_rank() returning a tier and RP number, the next job is converting that into something you can log and compare run over run. This function takes the raw result and figures out which of the 40 standard divisions it maps to, using the roughly-100-RP spacing from Step 1.

DIVISION_WIDTH = 100

def estimate_division(tier: str, rp: int) -> str:
    if tier == "Champion":
        return "Champion (no sub-division)"
    tier_floor = {
        "Copper": 0, "Bronze": 500, "Silver": 1000, "Gold": 1500,
        "Platinum": 2000, "Emerald": 2500, "Diamond": 3000
    }.get(tier, 0)
    offset = max(rp - tier_floor, 0)
    division_index = min(offset // DIVISION_WIDTH, 4)
    roman = ["V", "IV", "III", "II", "I"]
    return f"{tier} {roman[division_index]}"

This is an estimate, not an authoritative source, since exact RP thresholds can shift slightly between seasons as Ubisoft rebalances the curve. For your own rank, always trust the in-game Stats menu from Step 5 over anything a script calculates. The value of this function is purely for tracking relative movement over time, not for settling disputes about exact standing.

Step 10: Build a Rank-Change Notifier

Once you can fetch and parse a rank, the next useful piece is comparing today’s result against the last saved one and flagging a change. This keeps the script quiet when nothing’s happened and gives you a clear signal, printed to your terminal or piped into a desktop notification, when your RP actually moved.

import csv
import os
from datetime import datetime

LOG_FILE = "rank_history.csv"

def load_last_entry():
    if not os.path.exists(LOG_FILE):
        return None
    with open(LOG_FILE, newline="") as f:
        rows = list(csv.DictReader(f))
    return rows[-1] if rows else None

def log_and_notify(tier: str, rp: int, division: str):
    last = load_last_entry()
    timestamp = datetime.now().isoformat(timespec="seconds")
    new_row = {"timestamp": timestamp, "tier": tier, "rp": rp, "division": division}

    file_exists = os.path.exists(LOG_FILE)
    with open(LOG_FILE, "a", newline="") as f:
        writer = csv.DictWriter(f, fieldnames=new_row.keys())
        if not file_exists:
            writer.writeheader()
        writer.writerow(new_row)

    if last and int(last["rp"]) != rp:
        delta = rp - int(last["rp"])
        sign = "+" if delta > 0 else ""
        print(f"RP changed: {sign}{delta} -> now {division} ({rp} RP)")
    else:
        print(f"No RP change. Currently {division} ({rp} RP)")

This writes a growing CSV history and only prints a change notice when the number actually moves between runs, which is exactly what you want from something running in the background every so often rather than every time you glance at the terminal.

Step 11: Schedule the Script to Run Automatically

A script you have to remember to run manually defeats half the point. On macOS or Linux, add a cron entry to run it every 30 minutes. On Windows, Task Scheduler does the same job. Either way, don’t go faster than every 15 to 20 minutes; there’s no benefit to hammering a tracker site more frequently than ranked matches actually resolve, and it’s unnecessary load on a service you’re using for free.

# crontab -e, then add this line:
*/30 * * * * cd /path/to/r6-rank-tracker && ./venv/bin/python main.py >> run.log 2>&1

On Windows, open Task Scheduler, create a basic task, set the trigger to repeat every 30 minutes, and point the action at your virtual environment’s python.exe with main.py as the argument. Check the run.log file (or the Task Scheduler history) after the first couple of runs to confirm it’s actually firing before you walk away and trust it for a full session.

Step 12: Log and Chart Your Season Climb

With a few days of CSV history in rank_history.csv, you can turn the raw numbers into a chart that actually shows your climb, including the dips. This is genuinely motivating during a long ranked grind, since a day with three losses in a row feels worse in the moment than it looks once you can see the whole week’s trend line.

import csv
import matplotlib.pyplot as plt
from datetime import datetime

def plot_history():
    timestamps, rps = [], []
    with open("rank_history.csv", newline="") as f:
        for row in csv.DictReader(f):
            timestamps.append(datetime.fromisoformat(row["timestamp"]))
            rps.append(int(row["rp"]))

    plt.plot(timestamps, rps, marker="o")
    plt.title("RP Over Time")
    plt.xlabel("Date")
    plt.ylabel("RP")
    plt.xticks(rotation=45)
    plt.tight_layout()
    plt.savefig("rp_history.png")
    print("Saved chart to rp_history.png")

Run this once you’ve got at least five or six logged entries; a chart with two data points isn’t worth looking at. Over a full season, this same file becomes a genuinely useful record, letting you line up your RP swings against patch dates, operator bans, or simply which nights you played solo queue versus with a stack.

Common Pitfalls When Tracking R6 Siege Ranks

A handful of mistakes account for most of the confusion people run into, whether they’re checking their own rank or trying to figure out a streamer’s.

Searching a Twitch or social handle instead of the Ubisoft username. These are frequently different strings entirely, and tracker search boxes won’t guess for you.
Ignoring the platform filter. The same username can exist on PC, PlayStation, and Xbox as three unrelated accounts with three unrelated rank histories.
Treating peak RP as current RP. A profile showing a season-high number doesn’t mean that’s where the player sits today, especially after a losing streak.
Comparing RP across different seasons without accounting for the reset. Placement matches reshuffle standing at the start of every new season, so last season’s Diamond push means little for this season’s starting point.
Assuming a missing or empty tracker profile means the tool is broken. It’s far more often a privacy setting, a username mismatch, or indexing lag, as covered in Step 6.
Hammering a tracker site with a script running every minute. This risks getting your requests rate-limited or blocked, and it provides no real benefit since ranked matches take longer than a minute to resolve anyway.

Troubleshooting Your Rank Tracker

If something in the manual lookup or the Python script isn’t behaving, work through this list before assuming the underlying tool or site is broken.

Tracker search returns no results. Double-check the exact spelling and capitalization of the username, and confirm you’ve selected the correct platform filter.
Profile loads but shows old or stale data. The tracker may not have indexed your most recent matches yet; give it a few hours after a ranked session before concluding something is wrong.
Script’s extract_rank() returns None every time. The site’s page structure likely changed, or the profile you’re fetching is set to private. Open the URL manually in a browser first to confirm a rank is actually visible on the page before debugging the regex.
requests.exceptions.HTTPError on fetch. Check the response status code; a 403 usually means the site is blocking automated requests without a browser-like User-Agent, while a 404 means the profile URL itself is wrong.
Script runs but the CSV file never gets created. Confirm your script has write permission in the folder you’re running it from, and check that you’re running it from the project directory, not some other working directory.
Cron job never seems to fire. Use an absolute path to your virtual environment’s Python binary in the crontab line; cron doesn’t inherit your shell’s PATH or activated virtual environment.
Chart in Step 12 shows a flat, meaningless line. You likely only have one or two entries logged so far; let the tracker run for several sessions before judging the output.
Numbers in the script don’t match what you see in-game. Always trust the in-game Stats menu over any third-party tool or script; treat external sources as a convenience layer, not the source of truth.

Advanced Tips for Serious Rank Climbers

Once the basic tracker is running reliably, a few refinements make it genuinely useful rather than just a novelty. First, log your queue type alongside RP if the tracker page exposes it, since solo queue and full-stack queue often produce very different RP curves, and separating them in your CSV lets you see which mode is actually carrying your climb. Second, if you’re chasing Champion or trying to break into the new Legend Division, pay closer attention to session length rather than session count; RP tends to swing harder in the last few games of a long session as fatigue sets in, so a script that flags “you’ve logged four losses in the last 90 minutes” is more actionable than a daily summary.

Third, if you want to compare your own climb against a streamer’s publicly known numbers, like the broad viewer and engagement figures TwitchTracker publishes for Jynxzi’s September 2026 streams, remember you’re comparing two different kinds of data: your RP is a competitive rating, while a streamer’s viewer count is an audience metric. They’re interesting side by side, but they measure completely unrelated things, so resist the temptation to read deeper meaning into a streamer’s audience size as some kind of proxy for their actual skill or rank.

Fourth, consider tracking two separate CSV files if you play both ranked and the Legend Division’s solo-queue mode once you’re eligible for it. The two playlists measure different things under Ranked 3.0, and mixing their numbers into one chart will produce a misleading line that looks like a rank drop when it’s really just a mode switch. Keeping them apart also makes it easier to answer a question a lot of climbers eventually ask themselves: am I actually getting better, or did I just get lucky with easier lobbies this week? A season-long chart split by mode gives you an honest answer that a single stream title never will.

Comparing Your Tools: Trackers, Streams, and the Game Client

Different sources answer different questions, and knowing which one to reach for saves time.

Source	Shows RP/Rank	Shows Viewer Stats	Requires Login	Best Used For
In-game Stats menu	Yes, always current	No	Yes (your own account)	Your own authoritative rank
R6 Tracker Network	Yes, if profile is public and indexed	No	No, for lookups	Checking any public profile’s rank
TwitchTracker / similar	No	Yes	No	Streamer audience size and stream history
Your own Python tracker	Yes, estimated from a public profile	No	No	Logging and charting RP history over a season

This is also exactly why the “what rank is Jynxzi” question keeps resurfacing without a clean answer: the tool that would confirm it, R6 Tracker Network, depends on an indexed, public profile that his account doesn’t currently satisfy, while the tool that does have clear data about him, TwitchTracker, measures audience size rather than ranked standing entirely.

The Complete Working Project

Here’s every piece from Steps 7 through 12 combined into a single runnable script. Save it as main.py in the project folder you created in Step 7, replace PROFILE_URL with the tracker profile page you want to monitor, and run it with python main.py.

import csv
import os
import re
import requests
from datetime import datetime

PROFILE_URL = "https://example-tracker-site.com/profile/your-username"
LOG_FILE = "rank_history.csv"
TIERS = ["Copper", "Bronze", "Silver", "Gold", "Platinum",
         "Emerald", "Diamond", "Champion"]
HEADERS = {"User-Agent": "Mozilla/5.0 (personal rank tracker; contact: [email protected])"}

def fetch_profile_html(url: str) -> str:
    response = requests.get(url, headers=HEADERS, timeout=15)
    response.raise_for_status()
    return response.text

def extract_rank(html: str):
    pattern = r"(" + "|".join(TIERS) + r")\s*(?:[IVX]{1,3})?\s*[-,:]?\s*(\d{3,5})\s*RP"
    match = re.search(pattern, html, re.IGNORECASE)
    if not match:
        return None
    return {"tier": match.group(1).title(), "rp": int(match.group(2))}

def estimate_division(tier: str, rp: int) -> str:
    if tier == "Champion":
        return "Champion (no sub-division)"
    tier_floor = {"Copper": 0, "Bronze": 500, "Silver": 1000, "Gold": 1500,
                  "Platinum": 2000, "Emerald": 2500, "Diamond": 3000}.get(tier, 0)
    offset = max(rp - tier_floor, 0)
    roman = ["V", "IV", "III", "II", "I"]
    return f"{tier} {roman[min(offset // 100, 4)]}"

def load_last_entry():
    if not os.path.exists(LOG_FILE):
        return None
    with open(LOG_FILE, newline="") as f:
        rows = list(csv.DictReader(f))
    return rows[-1] if rows else None

def log_and_notify(tier: str, rp: int, division: str):
    last = load_last_entry()
    row = {"timestamp": datetime.now().isoformat(timespec="seconds"),
           "tier": tier, "rp": rp, "division": division}
    exists = os.path.exists(LOG_FILE)
    with open(LOG_FILE, "a", newline="") as f:
        writer = csv.DictWriter(f, fieldnames=row.keys())
        if not exists:
            writer.writeheader()
        writer.writerow(row)
    if last and int(last["rp"]) != rp:
        delta = rp - int(last["rp"])
        print(f"RP changed: {'+' if delta > 0 else ''}{delta} -> now {division} ({rp} RP)")
    else:
        print(f"No RP change. Currently {division} ({rp} RP)")

if __name__ == "__main__":
    html = fetch_profile_html(PROFILE_URL)
    result = extract_rank(html)
    if result is None:
        print("Could not find a rank on this profile. Check the URL and privacy settings.")
    else:
        division = estimate_division(result["tier"], result["rp"])
        log_and_notify(result["tier"], result["rp"], division)

Run it once manually first to confirm it finds your rank correctly before handing it off to cron or Task Scheduler from Step 11. Expect output that looks like this on a normal run:

$ python main.py
RP changed: +84 -> now Diamond III (3140 RP)

And on a run where nothing has changed since the last check:

$ python main.py
No RP change. Currently Diamond III (3140 RP)

From here, the project is yours to extend. A natural next step is piping the notification line into a desktop alert or a simple webhook post so you see a change the moment it happens rather than the next time you glance at a terminal window.

Frequently Asked Questions

What rank is Jynxzi in R6 Siege right now?
Based on his own stream titles through September 2026, including “CHAMPION PUSH w STACK” and “SOLO TO CHAMPION PC,” he’s actively playing at or pushing into Champion tier. No public tracker profile independently confirms his exact division or current RP as of this writing, for reasons covered in Step 6.

Why doesn’t Jynxzi show up on R6 Tracker Network?
The most likely explanations are a username or platform mismatch between his public identity and his Ubisoft account, a private stats setting, or indexing lag on an account that’s changed recently. All three are common and don’t imply anything unusual.

What is Ranked 3.0 in Rainbow Six Siege?
It’s the ranked system overhaul that launched June 2, 2026, during Year 11 Season 2, Operation System Override. It removed the old hidden MMR and made RP the single, visible rating used for both your displayed rank and matchmaking.

How many ranks are in R6 Siege?
Forty on the standard ladder: eight tiers (Copper through Champion), each split into five divisions except Champion. Since October 15, 2026, there’s also the Legend Division, a solo-queue leaderboard above Champion I added via the Operation Split Fire update.

How much RP do you gain or lose per match?
Roughly 80 RP per win or loss is the commonly reported figure, though the exact amount varies with your opponents’ average rank and individual match performance.

Do I need an API key to build the rank tracker in this tutorial?
No. The script in Steps 7 through 12 works by fetching a public profile page and parsing visible text for a rank pattern, since most tracker sites don’t publish a documented public API with keys for this kind of lookup.

Is it against the rules to scrape a tracker site for my own rank?
Always check a site’s terms of service before running automated requests against it. Keep your request frequency low, as outlined in Step 11, and identify your script honestly with a descriptive User-Agent string, as shown in Step 8.

Can I use this same tracker script for a different Rainbow Six Siege profile?
Yes. Swap the PROFILE_URL constant for any public tracker profile page, and the same tier-detection logic applies, since it’s built around Ranked 3.0’s tier names rather than any specific player’s data.