Rust Server TrendsSeismic network · station log
Recording Stations11,674 Players54,186 Active3,387 Wipes · 3 h89 48 h

Station XX-15274 · no signal

ShockTestingPVE

Offline 157.85.85.223:24586 checked 9d ago

pve
Connect
Players now
0/ 40
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,274
top 69%
Last wipe
9d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15274 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 40 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

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 peak
0players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 19 Oct, 01:16 UTC9d ago M0.0steady 0 – – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ABYSS | PvE | US | Vanilla | Noob Friendly NA · groups of 8+ · monthly · 53 on average
17/ 200
[EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding EU · groups of 8+ · monthly · 35 on average
17/ 200
[US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding NA · groups of 8+ · monthly · 32 on average
11/ 200
【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 EA · groups of 30+ · monthly · 22 on average
25/ 200
[PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly groups of 8+ · monthly · 21 on average
10/ 150
[EU/GER] Rust Norddeutschland PVE EU · groups of 8+ · biweekly · 18 on average
6/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on ShockTestingPVE?

ShockTestingPVE runs a procedural map of size 1,500 with seed 50000, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on ShockTestingPVE?

No gather rate appears in the name of ShockTestingPVE. The group limit is 8 players, the game's default. In pve mode, no player-versus-player fighting. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on ShockTestingPVE right now?

A reading taken now finds ShockTestingPVE offline; the most recent activity was 9 days 8 hours ago.

How does ShockTestingPVE rank against other Rust servers?

Over the last seven days, ShockTestingPVE recorded enough player hours to reach #15,274 worldwide, placing it in the top 69% of all ranked servers.

Server facts

How reliably does ShockTestingPVE stay online?

No contact with ShockTestingPVE right now, and the last recorded contact was 9 days 8 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 19 October 2026.

Where in the world is ShockTestingPVE hosted?

A region is not published by ShockTestingPVE. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 157.85.85.223:24586 is the address it uses.

What build of Rust does ShockTestingPVE use?

On Linux, ShockTestingPVE runs Rust network protocol 2634 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on ShockTestingPVE?

The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.

On what timetable does ShockTestingPVE run its wipes?

Too few wipes of ShockTestingPVE are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 9 days 8 hours.

Tags

What do the server tags on ShockTestingPVE mean?

These are the tags ShockTestingPVE publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): Slots: 40; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^p (PvE): The danger comes from the world, not from other players. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does ShockTestingPVE appear?

These Rust Server Trends lists include ShockTestingPVE: Rust community servers without the side modes and Rust PvE servers. You will find it under these 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.

Connecting

What steps get you onto ShockTestingPVE?

You can connect by pressing F1 in Rust and typing client.connect 157.85.85.223:24586 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp40
Max players Slots: 40.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167781
Build It runs game build 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Gameplay

^p
PvE The danger comes from the world, not from other players.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.