Solo Server
Offline 37.11.80.79:28015 checked 7h ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 24% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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 |
|---|---|---|---|---|
| Thu 22 Oct, 14:59 UTC5d ago | – | – | running | 1 |
| Tue 20 Oct, 06:21 UTC7d ago | – | – | – | 1 |
| Sun 18 Oct, 09:53 UTC9d ago | – | – | – | 0 |
| Sat 17 Oct, 09:28 UTC10d ago | – | – | – | 1 |
| Mon 12 Oct, 13:14 UTC15d ago | 1 | held half | 4.8 days | 1 |
| Mon 5 Oct, 12:55 UTC22d ago | 1 | held half | 7 days | 1 |
| Mon 5 Oct, 06:45 UTC22d ago | 1 | – | 0.3 days | 1 |
| Fri 2 Oct, 06:33 UTC25d ago | 1 | held half | 3 days | 1 |
| Thu 1 Oct, 02:48 UTC26d ago | 1 | – | 1.2 days | 1 |
| Mon 28 Sep, 23:22 UTC29d ago | 1 | held half | 2.1 days | 0 |
| Mon 28 Sep, 08:26 UTC29d ago | 1 | – | 0.6 days | 1 |
| Sat 26 Sep, 15:24 UTC31d ago | 1 | – | 1.7 days | 1 |
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| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 163 on average | 31 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 56 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 45 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 8 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14 / 1000 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for Solo Server: what is it?
The next wipe on Solo Server cannot be predicted, because it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The current world dates from 7 days 8 hours.
On Solo Server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 100% of cases.
Server
What is the hosting location of Solo Server?
A region is not published by Solo Server. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 37.11.80.79:28015 is its address.
What Rust build does Solo Server run?
On Windows, Solo Server runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.
Is Solo Server up, and how steady is its uptime?
Offline at this refresh: Solo Server, last seen 7 hours ago. 21% uptime over the last 7 full days, equal to 35 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.
Tags
How should the tags on Solo Server be read?
gmrust (Game mode): Rust survival, standard ruleset; mp10 (Max players): Capacity of 10 slots; ts0 (Group limit): Team play is disabled; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): The Modded section, because plugins or settings modify play are the tags Solo Server publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
On Rust Server Analytics, which lists and filters feature Solo Server?
Among the Rust Server Analytics lists Solo Server fits are: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 2 weeks.
Player numbers
Where does Solo Server sit among Rust servers?
On player hours over seven days, Solo Server ranks #5,303, within the top 24% of ranked servers.
How many players does Solo Server carry?
The last sighting of Solo Server was 7 hours ago; it is offline at this refresh. Averaging 1 players across seven days, the server reached a peak of 1. Across the last 48 hours, 06:00 UTC shows the highest average: 1 players.
Settings
What are the settings on Solo Server, and its rules?
Gather rate is not mentioned in the name of Solo Server. Group limits are not published. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. The Modded category lists it; plugins or settings change the game. The plugin framework is Oxide. Anti-cheat status: VAC on.
How to join
How do you connect to Solo Server?
In the Rust console (F1), enter client.connect 37.11.80.79:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.