Offline 81.108.209.47:28015 checked 16d ago
ppacket-test
Connect
srv = rust.server("81.108.209.47: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 61% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 18:22 UTC17d 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
- 81.108.209.47:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 18:22 UTC
- hostname
- –
- first seen
- 12 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 253 on average | 230/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 271/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 106 on average | 77/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 26/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 57/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 39/100 |
Quick answers
From the figures on this page.
Player counts
What position does ppacket-test take in the server rankings?
Over the last seven days ppacket-test sits at #13,125 on player hours, in the top 61% of ranked servers.
What population does ppacket-test carry?
ppacket-test returns no live count at this refresh, having last been seen 16 days 2 hours ago.
Server facts
Which Rust version is ppacket-test on?
The build is Rust network protocol 2634 and build 167584 on Windows, run by ppacket-test. The protocol has to match before you can join, and Steam does the updating.
How reliable is ppacket-test, and is it online now?
ppacket-test is offline at this refresh; the last response came 16 days 2 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 12 October 2026.
In which location is ppacket-test hosted?
For ppacket-test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 81.108.209.47:28015.
Settings and map
Which rules apply on ppacket-test, and what settings?
You will not find a gather rate in the string ppacket-test. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. It appears under Modded, where plugins or settings change how the game plays. 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
On what schedule does ppacket-test wipe?
A rhythm cannot be read from the wipes of ppacket-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. This world was created 17 days 2 hours ago.
On ppacket-test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began.
Tags and filters
Which lists on Rust Data hold ppacket-test, and which filters?
The Rust Data lists that ppacket-test fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on ppacket-test?
The game's server browser reads these tags from ppacket-test: 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): To join, your game must run protocol 2634; cs167584 (Build): Recorded game build: 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into ppacket-test?
In Rust, F1 opens the console: type client.connect 81.108.209.47:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.