What Rust Player Data Can a Lookup Show?

Identity fields answer the first question: which account is this?

A lookup may show:

• SteamID64
• Current Steam profile name
• Avatar
• Profile URL
• Vanity URL where available
• Profile visibility
• Account creation date
• Account age

The SteamID64 is the stable part. Names, avatars, and vanity URLs can change.

That is why RustPlayerLookup should keep the numeric account ID visible on the result page.

When public and supported, the result may include:

• Rust playtime
• Available gameplay statistics
• Data recorded by a supported Rust source
• Last checked time
• Source or freshness context

Not every stat represents the player's full Rust history.

A number can be tied to one source, one group of servers, one mode, or one tracking period. The page should explain that scope instead of presenting every number as global.

Use the Rust player stats page for a closer look at hours, account age, and common stat limits.

Some services can return public account status or ban related fields.

These fields should be displayed carefully.

A ban record can require context. An old record, a game-specific ban, and a server action do not all mean the same thing. RustPlayerLookup should identify the source and avoid turning one field into a label for the entire person.

A lookup is context, not a moderation decision.

A missing field usually has one of four causes.

The profile is private

Steam privacy settings can hide game details and playtime.

The source does not track that field

One source may return identity data while another returns gameplay data.

The source is delayed

Data can be cached or refreshed on a schedule.

The request failed

A temporary upstream error should be shown as an availability problem, not as a zero value.

These cases should have different messages on the result page.

A result should show when it was checked.

If a cached result is used, say so.

If the source provides its own update time, keep that separate from the time RustPlayerLookup fetched it.

Useful labels include:

• Checked now
• Last checked 12 minutes ago
• Source updated 2 hours ago
• Cached result
• Temporary source delay

Do not use a fresh timestamp to make old source data look current.

A player lookup cannot prove a final claim about skill, conduct, honesty, or intent.

It can help answer narrower questions:

• Is this the correct account?
• Is the profile public?
• How old is the account?
• Are public Rust hours available?
• What statistics are available from the source?
• Is the result recent enough to use?
• Does the account need a closer investigation?

That is the right role for a fast lookup.

RustPlayerLookup is designed for speed. It should resolve the account and return a useful first read with minimal friction.

RustWho is designed for depth. It is the better destination when the account needs advanced investigation, richer history, private hours context, deeper ban context, alerts, or premium tools.

The two products should not hide the same basic data behind two different pages. RustPlayerLookup handles the quick read. RustWho handles the deeper workflow.