Offline 31.50.84.204:28015 checked 16d ago
ppacket-test
Connect
srv = rust.server("31.50.84.204:28016")
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
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
- 31.50.84.204:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 19:34 UTC
- hostname
- –
- first seen
- 11 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 · 157 on average | 98/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 101/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 87/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 29/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Player counts
How does ppacket-test compare in the rankings?
Player hours over seven days put ppacket-test at #15,568, in the top 71% of the ranked set.
How many players does ppacket-test hold at once?
ppacket-test returns no live count at this refresh, having last been seen 16 days 14 hours ago.
Server facts
Which Rust version is ppacket-test on?
Version Rust network protocol 2634 and build 167398 on Windows is reported by ppacket-test. Steam updates your game for you, but the protocol must match to join.
Is ppacket-test up, and what does its uptime show?
ppacket-test is offline at this refresh; the last response came 16 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 11 October 2026.
In which location is ppacket-test hosted?
For ppacket-test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 31.50.84.204:28015.
Map and rules
Which rules apply on ppacket-test, and what settings?
No gather rate appears in the name: ppacket-test. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has ppacket-test loaded?
The game generates its map: procedural, on ppacket-test.
Wipe schedule
When does ppacket-test wipe, and on what schedule?
A rhythm cannot be read from the wipes of ppacket-test 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 17 days 2 hours ago.
Tags and filters
Where does ppacket-test appear among Rust Data lists and filters?
On Rust Data, ppacket-test 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.
How should you read the server tags on ppacket-test?
These tags are published by ppacket-test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is 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.
Connecting
What is the way into ppacket-test?
The manual route: launch Rust, F1, then client.connect 31.50.84.204:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.