Ever wonder how to check who is on your Rust server? Maybe you are playing with someone fun and want to add them on Steam. Maybe that person is cheating and you want to report them. There are several ways to do it, and which one you use depends on whether you are in the game, in the panel, or on your phone.
| You want to… | Use | Admin needed? |
|---|---|---|
| See players on any server you are playing on | Steam overlay → View Players | No |
| See players on your server, in game | status in the F1 console | Yes |
| See players without launching Rust | status in the panel Console tab | No (panel access is enough) |
| Check from a phone or browser | WebRCON | Yes (RCON password) |
This works on every server, including ones you do not own, and needs no mods or admin rights.
While in Rust, open the Steam overlay with Shift+Tab, then click View Players under Friends.
That gives you everyone currently connected, and from there you can message them, add them, or report them.
The server-side answer is the status command. You can run it in three places:
statusThe output lists every connected player along with their SteamID, name, ping, connection time, IP address, anti-hack violation level and kick count:
hostname: My Rust Server
version : 2546 secure (secure mode enabled, connected to Steam3)
map : Procedural Map
players : 2 (100 max) (0 queued) (0 joining)
id name ping connected addr violation kicks
76561198000000001 "Alice" 24 1832.41 198.51.100.24:52033 0.0 0
76561198000000002 "Bob" 57 604.19 203.0.113.88:52011 0.0 0| Column | What it tells you |
|---|---|
id | The player's SteamID64. Paste it after https://steamcommunity.com/profiles/ to open their Steam profile. |
name | Their in-game display name. This can be changed, so match on the SteamID when banning. |
ping | Round-trip latency in milliseconds. Consistently high ping usually means the player is far from your server region. |
connected | Seconds since they joined. |
addr | Their IP and port. |
violation | Anti-hack violation score. A climbing number is worth investigating, though it is not proof on its own. |
kicks | How many times they have been kicked this session. |
Rust has a few commands in this area and they return different shapes of data. players and users both list connected players in a more compact form than status. The full reference lives in our Rust admin commands guide.
Rust ships WebRCON, a WebSocket-based remote console. It is not the legacy TCP Source RCON protocol, so tools built for other Source games will not connect. Facepunch maintain the official web client at facepunch.github.io/webrcon.
You need two things from your hosted Rust game server: the RCON port (28016 by default, one above your game port) and the RCON password, both on the Startup tab. Once connected you can run status and every other admin command exactly as you would in game.
Keep your RCON password private. Anyone with it has full control of your server. Treat it like a root password, and change it if you ever paste it into a screenshot or a support ticket.
status is a snapshot — it only shows who is connected at this instant. If you need to know who was on earlier, use one of these instead:
status do nothing when I type it?You are not admin. Running it in game needs an auth level — set ownerid or moderatorid and then server.writecfg, or just run the command from the panel Console tab instead, which is already authenticated.
Only through the Steam overlay method above, or a public tracker. Server commands require admin on that specific server.
Take the SteamID64 from the id column and open https://steamcommunity.com/profiles/<steamid>.