If a Steam profile is private, you can still see the important parts of a Rust player: VAC and game bans, project bans, real hours on servers, the server list, when they are online and the names they joined under. A private profile hides Steam hours, the game library, the friend list, the inventory and combat stats. The account creation date is usually hidden as well. You can still check the player by profile link or SteamID.
What is visible and what is not
| Data | Public profile | Private profile |
|---|---|---|
| Steam VAC and game bans | Visible | Visible |
| Project bans | Visible | Visible |
| Real hours on servers | Visible | Visible |
| Servers and online times | Visible | Visible |
| Names seen on servers | Visible | Visible |
| Rust hours on Steam | Visible if game details are public | Hidden |
| Combat stats: K/D, accuracy | Visible if game details are public | Hidden |
| Friend list and friends’ bans | Visible if the list is public | Hidden |
| Inventory | Visible if public | Hidden |
| Account creation date | Visible | Usually hidden |
The difference is where the data comes from. Whatever Steam itself stores about the profile, privacy hides. Whatever servers and project admins recorded does not depend on Steam settings.
Privacy can be partial
Steam does not only let you lock the whole profile. You can keep the profile public but hide game details, or hide just the friend list. That is why the report uses different labels: "Profile is private", "Games and playtime hidden", "Playtime hidden", "Friend list empty or hidden". Each one tells you exactly what is missing.
Bans are always visible
Steam returns VAC and game bans regardless of privacy. How many there are and how many days since the last one is visible on any profile.
Project bans are a separate story. They are manual decisions by admins of Russian servers, and Steam knows nothing about them. The projects publish them, and they are tied to the SteamID, not to profile settings. What kinds of bans exist and how to read the reason is covered in how to check a player’s bans.
Hours: hidden, not secret
A private profile hides Steam hours but not server sessions. The server saw the player and recorded it. So real hours, the time actually spent on servers, are known even behind a private profile. What you lose is the comparison with Steam hours, and with it the check for padded hours.
There is also a loophole. If the player wrote a Steam review of Rust, Steam prints their hours next to the review even when the profile hides them. The report finds that review and marks the hours as taken "from a review".
More on that in hidden hours in Rust and how to find a player’s real hours.
Is a private profile a red flag?
Not on its own. People go private for all sorts of reasons: they do not want to show off their inventory or friends, or it is just habit. The report counts a private profile as a weak signal and says plainly that key data is hidden and the assessment is incomplete.
What raises eyebrows is a combination: private profile, fresh account, few real hours and project bans. Then the privacy looks less like a coincidence. How to read account age is covered in account age and cheaters.
How to check a private profile
- Get the SteamID64 or profile link. The number is visible even on a private profile, because it sits in the page address. If the address has a custom name, copy the whole link. More in how to find a player’s SteamID.
- Paste it into RustRecon. The report gathers everything available without the profile.
- Start with project bans. With a private profile, they carry the most weight. For free you see how many projects banned the player; Pro shows which ones, why and when.
- Look at real hours and servers (in Pro). Where they play, how much, and since when.
- Check the names (in Pro). A rename right after a project ban is worth noting.
A private profile does not hide a player from servers. If they play on servers tracked by BattleMetrics, their sessions, servers and names are visible whatever their Steam settings.
The report is not a cheat detector. It collects open data, and the call on whether to team with someone or wait for them by the door stays with you.