Working its way up from the back of the class: #15,274 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
51/ 100
D
Moving up: up 167 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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.
No daily history yet.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 19 Oct. 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
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 peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 19 Oct, 01:16 UTC10d ago
0
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
ShockTestingPVE leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 157.85.85.223:24586 is the address to use.
How dependable is ShockTestingPVE, and is it online at the moment?
At this moment, ShockTestingPVE is offline; the last time it was seen was 10 days 1 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 19 October 2026, Rust Server Score saw it for the first time.
What Rust version is ShockTestingPVE on?
You will find ShockTestingPVE 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.
Wipe cycle
On what schedule does ShockTestingPVE reset?
The record holds too few of ShockTestingPVE's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 10 days 2 hours have passed since this world was made.
What happens on ShockTestingPVE when wipe day arrives?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
Where does ShockTestingPVE place in the wider field of Rust servers?
In the top 69% of all ranked servers, ShockTestingPVE sits at #15,274 for player hours over the last seven days.
What does the population on ShockTestingPVE look like?
The last sighting of ShockTestingPVE was 10 days 1 hours ago, and it is offline right now.
Tags
What do ShockTestingPVE's tags stand for?
The game's browser takes its cue from the tags ShockTestingPVE has set: gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): 40 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^p (PvE): Players do not fight one another here; the world is the danger. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show ShockTestingPVE?
These Rust Server Score lists count ShockTestingPVE among them: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
Which rules does ShockTestingPVE enforce, and what are its settings?
Nothing in the name of ShockTestingPVE states a gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on ShockTestingPVE?
A procedural map of size 1,500 and seed 50000, generated by the game, is what ShockTestingPVE runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to ShockTestingPVE?
To connect, start Rust, press F1, and type client.connect 157.85.85.223:24586. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max players40 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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 momentum (D); standing is the one to work on (F).