Know who you're
queued with.
Check ranked stats, compare seasons, and see what contributes to a player’s suspicion score.
Ubisoft · Xbox · PlayStation
Top 5 popular profiles
From recent successful searches. Ranked stats are saved snapshots; unavailable values appear as —.
Profiles will appear here as players are searched.
SIDE-BY-SIDE ANALYSIS
Put two players’ stats in context.
Compare ranked K/D, win rate, kills per match and rank alongside suspicion scores and the signals behind them.
Open Compare- Ranked performanceSee where each player’s numbers differ.
- Score explanationsReview the statistical signals behind both scores.
- Share a comparisonSend a link to the side-by-side results.
How to check a player
Choose the right platform and use the name shown in game. Read the result alongside the match count and season history.
Find the profile
Search by the player's platform name. R6Intel loads available public profile and ranked data, then identifies the current account and season information.
Read the performance
Core statistics such as rank, K/D, win rate, headshot rate and match volume are presented first. Historical seasons provide context instead of treating one number in isolation.
Review the signals
The analysis weights ranked kills per match, K/D and headshot rate. Historical changes provide context. The result is a statistical suspicion score, not a ban prediction, accusation or determination of misconduct.
What the suspicion score means
The R6Intel score is an anomaly index from 0 to 100. Higher values mean the available statistics contain more unusual patterns under the current model. The score should be read alongside match count, data confidence, historical progression and the individual signals shown on the profile.
It is not a literal probability that a player is cheating. R6Intel does not replace Ubisoft enforcement, and normal players can occasionally produce unusual statistics.
Why results can change
Player statistics change as matches and seasons are played. R6Intel may serve a recent saved profile while a live refresh is running, and provider availability can affect how quickly fresh data appears.
Profile history helps preserve useful context over time instead of judging an account from a single search or a single match.