SOL13225
Solo
Offline 88.183.128.13:28015 checked 36d 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 57% 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.
-
01COMPlayers 140/250
-
02COMPlayers 105/200
-
03COMPlayers 14/250
-
04COMPlayers 17/250
-
05COMPlayers 12/100
-
06COMPlayers 19/200
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show Solo?
These Rust Tracker lists carry Solo: Community servers, no tags. These filters surface it on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Solo?
Listed for the server browser to read, Solo publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp1 (Max players): Slots: 1; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Schedule
On what schedule does Solo wipe?
The record holds too few of Solo's wipes to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. 36 days 3 hours since this world was made.
Location and Status
What is the uptime on Solo, and is it online?
Offline: Solo confirmed offline, last seen 36 days 1 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. The first sighting by Rust Tracker was 22 September 2026.
Which Rust build is Solo running?
Rust network protocol 2633 and build 165217 on Windows is what Solo runs. Steam updates it for you; your game must share the protocol to join.
Which location is Solo in?
No region is published by Solo. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 88.183.128.13:28015.
Player Count
What is the player count on Solo?
Offline now for Solo, last seen 36 days 1 hours ago.
How does Solo compare in the rankings?
Seven-day player hours put Solo at #13,225, within the top 57% of all ranked servers.
Settings
Which settings and rules are confirmed on Solo?
The name of Solo carries no gather rate. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build and raid: the standard game. Players can raid and fight each other here. Listed under Community in the server browser, it is a community server. VAC is on, Valve's anti-cheat.
What map is Solo on?
Procedural map on Solo, made by the game.
Connect
How do you get onto Solo?
Open the console in Rust with F1 after starting the game, then type client.connect 88.183.128.13:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp1,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp1
ts8
v2633
cs165217
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.