A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,344 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 219 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·WW····
·······
·W···WW
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 5.5
The first 48 hours of its last wipes
Sun 11 OctSat 10 OctTue 6 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 04:53 UTC18d ago
2
–
running
0
Sat 10 Oct, 12:25 UTC19d ago
2
–
0.7 days
0
Tue 6 Oct, 12:52 UTC23d ago
3
halved by day 3
4 days
1
Tue 6 Oct, 01:37 UTC23d ago
3
–
0.5 days
0
Wed 23 Sep, 13:16 UTC36d ago
2
halved by day 8
12.5 days
0
Tue 22 Sep, 13:57 UTC37d ago
2
–
1 days
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
Which region is PPP-僵尸/突袭/事件/车队 非常不纯净PVE based in?
You won't find a region tag on PPP-僵尸/突袭/事件/车队 非常不纯净PVE, but its name indicates Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. 43.249.192.111:6037 is the address to use.
Is PPP-僵尸/突袭/事件/车队 非常不纯净PVE up, and how steady is its uptime?
Right now, PPP-僵尸/突袭/事件/车队 非常不纯净PVE is online. It was up 99% of the time over the last 7 full days, 167 of 168 hours. The first sighting by Rust Server Score was on 15 September 2026.
On what Rust version does PPP-僵尸/突袭/事件/车队 非常不纯净PVE sit?
You will find PPP-僵尸/突袭/事件/车队 非常不纯净PVE on Rust network protocol 2634 and build 167781, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does PPP-僵尸/突袭/事件/车队 非常不纯净PVE reset?
No next wipe can be predicted for PPP-僵尸/突袭/事件/车队 非常不纯净PVE, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 18 days 10 hours have passed since this world was made.
What should you expect from wipe day on PPP-僵尸/突袭/事件/车队 非常不纯净PVE?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 1 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 5.5 is when it sank below half in the wipes that did not hold.
Player count
Where does PPP-僵尸/突袭/事件/车队 非常不纯净PVE sit among Rust servers?
Over the last seven days, PPP-僵尸/突袭/事件/车队 非常不纯净PVE has #15,344 for player hours, in the top 69% of all ranked servers.
Is PPP-僵尸/突袭/事件/车队 非常不纯净PVE a busy server?
PPP-僵尸/突袭/事件/车队 非常不纯净PVE is showing 0 players right now, with 50 slots in total. Over the past seven days, the average player count was 0.
Lists and filters
What is meant by the tags on PPP-僵尸/突袭/事件/车队 非常不纯净PVE?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags PPP-僵尸/突袭/事件/车队 非常不纯净PVE publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature PPP-僵尸/突袭/事件/车队 非常不纯净PVE?
These Rust Server Score lists count PPP-僵尸/突袭/事件/车队 非常不纯净PVE among them: Best community servers, graded. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on PPP-僵尸/突袭/事件/车队 非常不纯净PVE?
You will find no gather rate in the name of PPP-僵尸/突袭/事件/车队 非常不纯净PVE. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Connecting
What is the way to join PPP-僵尸/突袭/事件/车队 非常不纯净PVE?
Enter client.connect 43.249.192.111:6037 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 asmp50,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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. Strongest in uptime (A); population is the one to work on (F).