Solo
Offline 92.170.168.69:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
no slots published 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- 562/675
- 360/525
- 44/250
- 41/250
- 119/200
- 131/300
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 next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 47 days 21 hours ago the current world was made.
Lists and filters
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; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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?
Rust Metrics lists featuring Solo: 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.
Player count
What position does Solo hold among Rust servers?
Ranking for Solo: #15,150 on seven-day player hours, top – of all ranked servers.
What player count does Solo carry?
Solo is not responding; status offline, last seen 44 days 23 hours ago.
Server details
Which location does Solo run from?
Reading: location. Solo gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 92.170.168.69:28015.
What Rust version is Solo on?
Version check: Rust network protocol 2633 and build 163794 on Windows, 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 44 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
How is Solo configured, and what rules are in force?
Reading the name gives no gather rate for Solo. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
Which map is live on Solo?
Check: map. Procedural, generated by the game, on Solo.
Connection
How can you get onto Solo?
To join: start Rust, press F1 and type client.connect 92.170.168.69:28015. Or press Launch Rust here and Steam opens the game and connects you.