Solo
Offline 31.77.207.224:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| 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- 566/625
- 418/450
- 161/250
- 51/100
- 175/250
- 348/225
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Solo follow?
Its rhythm cannot be told from the wipes of Solo on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 40 days 4 hours ago.
Tags
Which tags does Solo carry, and what do they mean?
Tags published by Solo, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Solo appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Solo: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What position does Solo hold among Rust servers?
Ranking for Solo: #15,403 on seven-day player hours, top – of all ranked servers.
What is the population on Solo?
Status for Solo: offline. Last seen 40 days 4 hours ago.
Server
What location is Solo hosted in?
Reading: location. Solo gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 31.77.207.224:28015.
What Rust version is Solo on?
Version check: Rust network protocol 2633 and build 164530 on Linux, run by Solo. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is Solo, and is it online now?
Reading: offline. Solo last answered 40 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 September 2026, recorded by Rust Metrics.
Settings and map
How is Solo configured, and what rules are in force?
Reading the name gives no gather rate for Solo. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Solo?
Check: map. Procedural, generated by the game, on Solo.
Join
How can you get onto Solo?
To join: start Rust, press F1 and type client.connect 31.77.207.224:28015. Or press Launch Rust here and Steam opens the game and connects you.