RUST//RECON
Ban findings48 unique
VAC
22
Game + EAC
32
Unique SteamIDs · all time
Rust Recon public player research dashboard showing Steam identity, ban records, and combat statistics

Player intelligence console

Rust SteamID64 player lookup & recon

Search a Rust player by SteamID64, Steam profile, username, or BattleMetrics URL to review public identity, ban, activity, network, combat, and server signals.

G Continue with GoogleAuthentication is completed securely on the next screen. Every authenticated lookup is recorded for security and abuse prevention.
Public information only
Sign in to unlock
Import BattleMetrics results

Paste CSV, tab-separated, pipe-separated, or JSON rows up to 100 KB. Include Player, Server, and Last Seen. Optional columns are profile URL, server URL, ids, and address. Other columns are rejected. Data stays in this browser.

Evidence, not verdicts.Signals require context.

Latest improvements · October 18, 2026

What’s new in Rust Recon

Watchlist limits now apply consistently, monitoring prioritizes older scans, and production builds enforce type checking. Read maintenance updates.

See the newest production features and workflow improvements added for faster player and server research.

Rust player research

One lookup, connected public signals

Start with a stable Steam identifier, then review source-linked evidence instead of relying on a display name or a single score.

SteamID64 player lookup

Resolve a Steam profile, account maturity, Rust hours, aliases, level history, and available inventory value from a 17-digit SteamID64.

Ban and friend correlation

Compare visible VAC, game, EAC, community, blacklist, and public friend-network signals while keeping source disagreements clear.

BattleMetrics and server history

Connect BattleMetrics player records and participating Rust community statistics to review recent servers, playtime, and combat context.

How a Rust Recon report works

A lookup begins by resolving the player to a stable SteamID64 whenever possible. Rust Recon then requests available public records and connects matching identifiers across Steam, BattleMetrics player records, participating community statistics, ban sources, and stored observations. Each result identifies its source so you can open the original record and verify important findings. A username search may return several candidates because Rust display names are not unique.

How to interpret the risk score

The score is a review-priority indicator, not proof that somebody cheated. Visible bans carry more weight than indirect signals. Fresh accounts, unusual combat percentages, name changes, limited playtime, or banned friends can add context, but none establishes misconduct by itself. Source disagreement is shown prominently because an EAC, VAC, game, community, or server-ban result may appear in one system before it appears in another. See Facepunch’s official explanation of an EAC ban.

What public-profile limits mean

Steam privacy settings can hide friends, inventory, groups, games, or playtime from a live request. When Rust Recon previously observed public data for the same SteamID64, the report can label and reuse the latest stored observation instead of presenting missing live data as a confirmed zero. Cached information is dated because a friend list, inventory value, alias, or account status may have changed since it was captured. Steam documents these controls in its profile privacy guide.

When to run another scan

Rerun a report before making a time-sensitive decision. Ban records, player names, server activity, inventory prices, Steam levels, and profile visibility can change. Repeated scans also build a dated history that makes account changes easier to understand. For the strongest match, use a 17-digit SteamID64 or an exact Steam profile URL, then confirm consequential findings directly with the linked public source.

Run a Rust player lookup

Built for faster review

Turn scattered public records into one research workflow

Rust server owners and moderation teams can start with a SteamID64, compare source-linked signals, and save a dated report for later review.

FAQ

Quick answers

What should I search with first?

Use the player’s 17-digit SteamID64 when possible. It is more reliable than a display name, which can change or belong to several players.

Does the risk score prove cheating?

No. It ranks visible signals for review and is not a misconduct verdict. Confirm important findings with the original sources.

Can Rust Recon bypass a private profile?

No. Rust Recon uses public, user-provided, and third-party information where available. Private or restricted data remains unavailable.

When are combat statistics flagged?

Headshots at 25% or higher or accuracy at 40% or higher can independently raise review priority when enough hits or shots are recorded. Meeting both thresholds receives stronger weighting.

Why are some results unavailable?

Coverage depends on Steam privacy settings, public source availability, rate limits, and whether a community server publishes statistics for that player.

Are flagged friends evidence of an alternate account?

No. Friend bans or fresh accounts provide context only. Friendship and account age do not establish cheating or shared ownership.

Can I save the complete report?

Yes. After a full player query, select Export PDF. The report expands all evidence and keeps your selected light, dark, and color theme.

How current is a report?

Each report shows when it was checked. Public records can change, so rerun the SteamID64 before making a time-sensitive decision.