SoloLocal
Offline 223.74.89.123:28015 checked 1d 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
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 17/ 100
- 214/ 400
- 173/ 225
- 134/ 100
- 249/ 1000
- 20/ 700
Quick answers
Tags and search
Where does SoloLocal appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include SoloLocal: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
What's the meaning of the tags on SoloLocal?
The server browser shows these tags for SoloLocal: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): The slot count is 10; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): This server runs build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server info
What location is SoloLocal in?
No region comes from SoloLocal. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 223.74.89.123:28015.
How reliable is SoloLocal?
The server SoloLocal is not reachable at the moment; the last sighting was 27 hours ago. 17 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for SoloLocal?
Rust network protocol 2634 and build 167781 is what SoloLocal runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
What schedule does SoloLocal follow for wipes?
Too few wipes are on record for SoloLocal to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 30 hours is how long ago this world came into being.
Rules and settings
What settings and rules have been applied to SoloLocal?
Its name does not state a gather rate for SoloLocal. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Which map is active on SoloLocal?
The map on SoloLocal is procedural, made by the game.
Player count
How many players are on SoloLocal?
The last sighting of SoloLocal was 27 hours ago; it is offline right now. Over the past week it has drawn 0 players on average.
What's SoloLocal's rank among Rust servers?
For player hours in the last seven days, SoloLocal ranks #15,843, within the top 72% of ranked servers.
Getting in
What's the way to join SoloLocal?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 223.74.89.123:28015.