Offline 76.129.35.101:28015 checked 24d ago
SoloDoloGozo | Solo PvE
Connect
srv = rust.server("76.129.35.101: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 bestTop 71% 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 | Fri 2 Oct, 22:16 UTC26d ago | 1 | NaN | running | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 76.129.35.101:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 22:16 UTC
- hostname
- –
- first seen
- 2 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 · 155 on average | 28/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 33/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 3/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does SoloDoloGozo | Solo PvE rank?
Over the last seven days SoloDoloGozo | Solo PvE sits at #16,001 on player hours, in the top 71% of ranked servers.
How full does SoloDoloGozo | Solo PvE run?
SoloDoloGozo | Solo PvE returns no live count at this refresh, having last been seen 24 days 12 hours ago.
Server facts
Which Rust version is SoloDoloGozo | Solo PvE on?
The build is Rust network protocol 2634 and build 166652 on Windows, run by SoloDoloGozo | Solo PvE. Steam updates your game for you, but the protocol must match to join.
How reliable is SoloDoloGozo | Solo PvE, and is it up?
Offline now for SoloDoloGozo | Solo PvE, last seen 24 days 12 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 2 October 2026.
In which location is SoloDoloGozo | Solo PvE hosted?
No region is published by SoloDoloGozo | Solo PvE. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 76.129.35.101:28015 is its address.
Settings and map
Which rules apply on SoloDoloGozo | Solo PvE, and what settings?
You will not find a gather rate in the string SoloDoloGozo | Solo PvE. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has SoloDoloGozo | Solo PvE selected?
A procedural map runs on SoloDoloGozo | Solo PvE, generated by the game.
Wipes and dates
When does SoloDoloGozo | Solo PvE wipe, and how often?
The record for SoloDoloGozo | Solo PvE holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 26 days 3 hours ago, and that is the one in play.
What is wipe day on SoloDoloGozo | Solo PvE like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold SoloDoloGozo | Solo PvE, and which filters?
The Rust Data lists that SoloDoloGozo | Solo PvE fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on SoloDoloGozo | Solo PvE hold?
Read by the game's server browser, the tags SoloDoloGozo | Solo PvE publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way into SoloDoloGozo | Solo PvE?
Enter client.connect 76.129.35.101:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.