Offline 177.72.227.240:28015 checked 10d ago
PaperRust LOCAL validation
Connect
srv = rust.server("177.72.227.240: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 70% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 13:19 UTC10d ago | 0 | 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
- 177.72.227.240:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 13:19 UTC
- hostname
- –
- first seen
- 19 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 | 15/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 34/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 2/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 6/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 127/200 |
Quick answers
From the figures on this page.
Player counts
How does PaperRust LOCAL validation compare in the rankings?
Player hours over seven days put PaperRust LOCAL validation at #15,318, in the top 70% of the ranked set.
What population does PaperRust LOCAL validation carry?
PaperRust LOCAL validation returns no live count at this refresh, having last been seen 10 days 10 hours ago.
About the server
Which Rust version is PaperRust LOCAL validation on?
Rust network protocol 2634 and build 167781 on Linux is what PaperRust LOCAL validation runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is PaperRust LOCAL validation, and is it online now?
PaperRust LOCAL validation 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 19 October 2026.
Where does PaperRust LOCAL validation sit?
There is no region published for PaperRust LOCAL validation. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 177.72.227.240:28015.
Rules, settings, map
Which rules apply on PaperRust LOCAL validation, and what settings?
You will not find a gather rate in the string PaperRust LOCAL validation. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has PaperRust LOCAL validation selected?
The game generates its map: procedural, on PaperRust LOCAL validation.
Wipe schedule
When does PaperRust LOCAL validation wipe, and how often?
A rhythm cannot be read from the wipes of PaperRust LOCAL validation on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 10 days 12 hours ago.
On PaperRust LOCAL validation, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which Rust Data filters and lists contain PaperRust LOCAL validation?
These Rust Data lists include PaperRust LOCAL validation: 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 2 weeks.
How should you read the server tags on PaperRust LOCAL validation?
Read by the game's server browser, the tags PaperRust LOCAL validation publishes are: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. 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
What is the way to join PaperRust LOCAL validation?
Enter client.connect 177.72.227.240:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.