Solo
Offline 188.243.237.226:28015 checked 9d 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 bestTop 69% 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- 393/400
- 346/350
- 38/250
- 32/250
- 47/100
- 151/200
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Solo follow?
The rhythm of Solo's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 9 days 15 hours ago the current world was made.
Tags
How should you read the tags on Solo?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Solo. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Solo?
On Rust Metrics, Solo sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Player count
Where does Solo sit in the rankings?
Player hours over seven days put Solo at #15,328, in the top 69% of all ranked servers.
What is the population on Solo?
Status for Solo: offline. Last seen 9 days 14 hours ago.
Server details
Where does Solo sit?
Reading: location. Solo gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 188.243.237.226:28015.
What Rust version is Solo on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by Solo. Check: protocol. To join, your game must match; Steam handles the update.
Is Solo up, and how often does it stay up?
Reading: offline. Solo last answered 9 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 October 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on Solo?
Check: gather rate. The name Solo does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Solo?
Procedural map on Solo, made by the game's generator.
Connection
How do you connect to Solo?
To join: start Rust, press F1 and type client.connect 188.243.237.226:28015. Or press Launch Rust here and Steam opens the game and connects you.