Solo
Offline 31.77.207.224:28015 checked 39d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Rules and settings
On Solo, which rules and settings apply?
The name of Solo does not state a gather rate. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. The server browser lists it under Community; it is a community server. The server has VAC, Valve's anti-cheat, turned on.
What is the map on Solo?
Solo runs a procedural map, which the game generates.
Lists and filters
On Rust Server Index, which lists and filters carry Solo?
Filed under these Rust Server Index lists is Solo: Community Rust servers, indexed. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is meant by the tags on Solo?
These are the tags Solo publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp1 (Max players): Player cap: 1; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Joining needs you on game protocol 2633; cs164530 (Build): Build on file: 164530; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipes and resets
When does Solo wipe?
Its rhythm is not yet clear, since the record holds too few of Solo's wipes. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 39 days 13 hours is when its current world was made.
Players and ranking
How is Solo ranked compared with the rest?
Filed under rankings: #15,403 for Solo on seven-day player hours, top – overall.
What does the player count on Solo look like?
At present Solo is offline; its last sighting was 39 days 13 hours ago.
Server details
Which Rust build is Solo running?
Rust network protocol 2633 and build 164530, on Linux, is what Solo runs. To join you need the same protocol; Steam handles the update.
Is Solo reachable, and does it stay up?
As of now Solo is offline, with its last appearance 39 days 13 hours ago. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 19 September 2026 it was first seen by Rust Server Index.
Where in the world is Solo hosted?
Solo gives no region at all. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 31.77.207.224:28015.
Connecting
How can you connect to Solo?
Enter client.connect 31.77.207.224:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp1,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp1
ts8
v2633
cs164530
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.