solo
Offline 95.26.212.66:28015 checked 23d 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
Top 71% 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.
Map and rules
Where can you read the rules and settings that apply on solo?
No gather rate appears in the name solo. The group limit is 8 players, the game's default. The server runs survival, gather, build and raid: the standard game. PvP and raiding are allowed. Filed under Community in the server browser, it is a community server. VAC, Valve's anti-cheat, is enabled.
What is the map on solo?
solo runs a procedural map, which the game generates.
Tags
Which lists and filters on Rust Server Index is solo filed under?
The Rust Server Index lists that include solo are Community Rust servers, indexed. Filed under these filters 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 listed for solo?
The server's own tags are listed here, and the game's server browser reads them: solo gives gmrust (Game mode): Survival on standard Rust rules; mp500 (Max players): Player cap: 500; ts8 (Group limit): The team limit is 8, as in the standard game; v2634 (Protocol): Your client must run protocol 2634 to connect; cs166652 (Build): It runs build 166652; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): No region code has been set. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
When does solo wipe?
solo's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. Its present world dates from 25 days 1 hours.
Player counts
Where does solo sit in the rankings?
Filed under rankings: #16,003 for solo on seven-day player hours, top 71% overall.
Is solo quiet or crowded?
At present solo is offline; its last sighting was 23 days 23 hours ago.
Server facts
What Rust version is solo on?
Rust network protocol 2634 and build 166652, on Windows, is what solo runs. To join you need the same protocol; Steam handles the update.
What is the uptime and current status of solo?
As of now solo is offline, with its last appearance 23 days 23 hours ago. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 4 October 2026 it was first seen by Rust Server Index.
Which region is solo in?
No region is published by solo. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 95.26.212.66:28015.
Joining the server
What steps lead onto solo?
Enter client.connect 95.26.212.66:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp500,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
mp500
ts8
v2634
cs166652
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.