Offline 81.177.189.7:28015 checked 10d ago
Solo
Connect
srv = rust.server("81.177.189.7:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 18 Oct, 20:05 UTC11d ago | 1 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 81.177.189.7:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 20:05 UTC
- hostname
- –
- first seen
- 18 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 75/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 137/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 44/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 133/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
How does Solo compare in the rankings?
Rank #14,774 on seven-day player hours for Solo, within the top 67% of all ranked servers.
How many players does Solo hold at once?
The current row shows Solo offline; the last response was 10 days 10 hours ago.
Server data
What is the Rust version on Solo?
Version Rust network protocol 2634 and build 167781 on Windows is reported by Solo. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Solo, and is it up?
Solo is offline at this refresh; the last response came 10 days 10 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 18 October 2026.
Which location does Solo run from?
No region is published by Solo. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 81.177.189.7:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Solo?
The name Solo carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on Solo?
The game generates its map: procedural, on Solo.
Wipes and dates
On what schedule does Solo wipe?
A rhythm cannot be read from the wipes of Solo on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 11 days ago.
On Solo, what happens on wipe day?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does Solo appear among Rust Data lists and filters?
On Rust Data, Solo appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on Solo?
These tags are published by Solo and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Solo?
In Rust, F1 opens the console: type client.connect 81.177.189.7:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.