Offline 176.60.52.61:60741 checked 6d ago
RPV automatic local test
Connect
srv = rust.server("176.60.52.61:60742")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 176.60.52.61:60741
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 06:12 UTC
- hostname
- –
- first seen
- 22 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 · 153 on average | 34/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 47/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 1/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 2/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does RPV automatic local test rank?
Player hours over seven days put RPV automatic local test at #15,349, in the top 69% of the ranked set.
How full does RPV automatic local test run?
RPV automatic local test returns no live count at this refresh, having last been seen 6 days 22 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does RPV automatic local test run?
Rust network protocol 2634 and build 167781 on Windows is what RPV automatic local test runs. The protocol has to match before you can join, and Steam does the updating.
Is RPV automatic local test up, and what does its uptime show?
The latest sample has RPV automatic local test offline, with a last sighting 6 days 22 hours ago. Uptime of 0% across the last 6 full days: 0 hours of 144. Rust Data logged it first on 22 October 2026.
Which location does RPV automatic local test run from?
For RPV automatic local test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 176.60.52.61:60741 is its address.
Rules, settings, map
Which settings and rules does RPV automatic local test run?
The name RPV automatic local test carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. Anti-cheat status: VAC on.
What is the map on RPV automatic local test?
RPV automatic local test runs a procedural map, which the game generates.
Wipes and dates
On what schedule does RPV automatic local test wipe?
A rhythm cannot be read from the wipes of RPV automatic local test on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 6 days 22 hours ago.
Lists and tags
Which lists on Rust Data hold RPV automatic local test, and which filters?
These Rust Data lists include RPV automatic local test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on RPV automatic local test?
The game's server browser reads these tags from RPV automatic local test: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. 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 RPV automatic local test?
The manual route: launch Rust, F1, then client.connect 176.60.52.61:60741. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.