SoloLocal
Offline 223.74.89.123:28015 checked 10d ago
Vital stats
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
Top 70% 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
| 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.
Server tags
Which Rust Pop Watch lists and filters include SoloLocal?
You'll find SoloLocal on the following Rust Pop Watch lists: Modded Rust servers, live. These are the filters that list it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What do the server tags on SoloLocal mean?
The game's server browser picks up these tags from SoloLocal: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game must be on the same protocol version: 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. Current players, queue and world age are in the tags too, displayed at the top of this page.
Population
How does SoloLocal rank against other Rust servers?
A seven-day player-hours placing of #15,233 puts SoloLocal in the top 70% of all ranked servers.
How many players are on SoloLocal right now?
The last sighting of SoloLocal was 10 days 17 hours ago, and it is offline now.
Server facts
Is SoloLocal online, and how reliable is it?
The server SoloLocal is not online now; 10 days 17 hours have passed since it was last seen. It was up 0% of the time over the last 7 full days, 0 of 168 hours in total. The first time Rust Pop Watch saw it was 17 October 2026.
Where is SoloLocal located?
There is no region from SoloLocal. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 223.74.89.123:28015.
Which Rust version is SoloLocal on?
On Windows, SoloLocal runs Rust network protocol 2634 and build 167781. Joining requires your game to match the protocol, which Steam updates for you.
Wipe days
What is the wipe schedule on SoloLocal?
Too few wipes are on record for SoloLocal to reveal its rhythm. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. The world it is running now dates from 10 days 20 hours.
Rules and settings
Which map does SoloLocal run?
SoloLocal uses a procedural map, which the game generates.
What are the rules and settings on SoloLocal?
The name of SoloLocal says nothing about gather rate. Eight players per group: that is the game's default. survival is the game mode, gather, build and raid, as standard. Raids and PvP are both on the table. Plugins or settings alter the game, and the browser lists it as Modded. Oxide plugins are running on it. Anti-cheat is on: VAC, Valve's system.
Join up
How do I join SoloLocal?
The console method: start Rust, press F1, and type client.connect 223.74.89.123:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.