On the class lists: F (38), with population over 48 hours and no performance mark.
Players now0/ 700% full
7-day average0peak 2
Rank#6,889top 31%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 70 on average. Plenty of space to grow.
Standingrank on player hours
69/ 100
C+
Working its way up from the back of the class: #6,889 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 70 server fps on average.
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
27/ 100
F
Lost ground: down 3,173 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in performance (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
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 31% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
····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.
usual gap14.2 daysbetween real wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 5
The first 48 hours of its last wipes
Fri 16 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 3, 28 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 01:51 UTC13d ago
3
–
running
1
Thu 1 Oct, 21:51 UTCFW27d ago
3
halved by day 5
14.2 days
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
Which region is Chill PVE for hard workers based in?
You'll find no region listed by Chill PVE for hard workers. Rust Server Score takes the server's word for its location and does not trace the hardware. 104.192.227.10:28015 is the address to use.
How dependable is Chill PVE for hard workers, and is it online at the moment?
Right now, Chill PVE for hard workers is online. According to its reported uptime, the last restart was about 6 days 16 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does Chill PVE for hard workers run?
The average over the last 48 hours was 70 server fps, and it never went below 53. Buildings, deployables and everything else in the world added up to as many as 216,467 entities. Up to 8,078 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is Chill PVE for hard workers running?
Rust network protocol 2635 and build 168909 on Windows is what Chill PVE for hard workers runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does Chill PVE for hard workers reset?
The record holds too few of Chill PVE for hard workers's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 13 days 16 hours have passed since this world was made.
What should you expect from wipe day on Chill PVE for hard workers?
Recent wipes have peaked at 3 players on average. 28 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 5 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Chill PVE for hard workers place in the wider field of Rust servers?
In the top 31% of all ranked servers, Chill PVE for hard workers sits at #6,889 for player hours over the last seven days.
What does the population on Chill PVE for hard workers look like?
With 70 slots available, Chill PVE for hard workers currently has 0 players. The seven-day average is 0 players, with a peak of 2. Over the last 48 hours, the peak hour was 00:00 UTC, averaging 0 players.
Tags
What do Chill PVE for hard workers's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp70 (Max players): Its slot count is 70; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Chill PVE for hard workers 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 Chill PVE for hard workers?
Rust Server Score lists that include Chill PVE for hard workers: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is Chill PVE for hard workers set up, and what rules does it keep?
The name of Chill PVE for hard workers gives no gather rate. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Chill PVE for hard workers runs which map?
The game generates the procedural map on Chill PVE for hard workers at size 6,000 with seed 3343399825. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join Chill PVE for hard workers?
To connect, start Rust, press F1, and type client.connect 104.192.227.10:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp70,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp70
Max playersIts slot count is 70.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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. Strongest in performance (A+); population is the one to work on (F).