solo
Offline 222.234.32.188:28015 checked 3d 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 53% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 09:47 UTC8d ago | 1 | – | running | 0 |
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
- 139/ 200
- 302/ 300
- 242/ 275
- 781/ 800
- 104/ 200
- 104/ 250
Quick answers
Tags and filters
Where does solo appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry solo are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What's the meaning of the tags on solo?
solo's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp50 (Max players): The slot count is 50; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167231 (Build): It's on build 167231; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the location of solo?
There is no published region for solo. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 222.234.32.188:28015.
How reliable is solo?
The server solo is not reachable at the moment; the last sighting was 3 days 17 hours ago. It was up 2% of the time over the last full 7 days, 3 of 168 hours. The first sighting by Rust Going Deep was on 9 October 2026.
What is the Rust version for solo?
Rust network protocol 2634 and build 167231 is what solo runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
How often does solo wipe?
The wipes recorded for solo are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 8 days 17 hours ago.
What happens on wipe day at solo?
Across its recent wipes, the average busiest point drew 1 players. On the latest wipe, 0 hours passed before the crowd peaked.
Settings and map
What settings are in place on solo?
The name of solo contains no gather rate. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. The server browser lists it under Community, making it a community server. The server runs Valve's anti-cheat, VAC.
Which map is active on solo?
A procedural map, generated by the game, is in play on solo.
Population
Is solo busy?
Right now solo is offline, with its last appearance 3 days 17 hours ago. The seven-day average is 1 players, with a peak of 1.
Where does solo sit in the rankings?
Over the last seven days, solo is #11,755 by player hours, among the top 53% of all ranked servers.
Getting in
How do you get into solo?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 222.234.32.188:28015.