Working its way up from the back of the class: #13,125 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
31/ 100
F
Lost ground: down 5,031 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
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
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 18:22 UTC16d ago
1
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
ppacket-test leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 81.108.209.47:28015.
How dependable is ppacket-test, and is it online at the moment?
You cannot join now: ppacket-test is offline, last seen 15 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 12 October 2026.
Which Rust version is ppacket-test running?
Rust network protocol 2634 and build 167584 on Windows is what ppacket-test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does ppacket-test reset?
ppacket-test has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 16 days 4 hours.
What happens on ppacket-test when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 1 hours into the latest wipe.
Population
Where does ppacket-test sit among Rust servers?
In the top 61% of all ranked servers, ppacket-test sits at #13,125 for player hours over the last seven days.
What does the population on ppacket-test look like?
ppacket-test is offline at the moment; the last time it was seen was 15 days 4 hours ago.
Tags and filters
What is meant by the tags on ppacket-test?
The game's browser takes its cue from the tags ppacket-test has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167584 (Build): This runs on build 167584; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature ppacket-test?
Rust Server Score lists that include ppacket-test: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is ppacket-test set up, and what rules does it keep?
The name of ppacket-test gives no gather rate. With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Can you tell me which map ppacket-test uses?
A procedural map, generated by the game, is what ppacket-test runs.
How to join
What is the way to join ppacket-test?
Enter client.connect 81.108.209.47:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,^p,gmrust,cs167584,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167584
BuildThis runs on build 167584.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Even marks across the subjects, from F to F.