RUST METRICSFlight deck · live data
Data live Servers11,701 Players54,561 Populated3,263 Fresh wipes 3 h144 Scan5 min
‹ All servers104.192.227.10:28015
Online Full Queue Fresh wipe Wipe due No query

Chill PVE for hard workers

Online 104.192.227.10:28015 checked 12m ago

moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 08:00 UTC
0 18 35 52 70 PAX 0 /70

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 80 SERVER FPS

Server fps

48 h low 53 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 216,311 ×1000

Entities

48 h range 213,889–216,467 · memory 6,613 MB
1239 ET SINCE RESTART 6D 07H

Uptime

6 days 7 hours since its last restart, at the last reading
7-day average0peak 2
Rank#6,638top 30%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Memory6,613MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75111:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

REC 2

Server performance

025507510011:0020:0005:0013:0023:0008:00

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

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
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 28 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 01:51 UTC13d ago 3 – running 1
Thu 1 Oct, 21:51 UTC FW27d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on Chill PVE for hard workers when wipe day comes?

At their busiest, its recent wipes drew 3 players on average. Peak crowd on the latest wipe: 28 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 5 when it didn't.

How often does Chill PVE for hard workers wipe, and when?

Its rhythm cannot be told from the wipes of Chill PVE for hard workers on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 13 days 8 hours ago.

Tags

How should you read the tags on Chill PVE for hard workers?

Tags published by Chill PVE for hard workers, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp70 (Max players): 70 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Chill PVE for hard workers?

These Rust Metrics lists carry Chill PVE for hard workers: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up 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.

Occupancy

Where does Chill PVE for hard workers sit in the rankings?

Player hours over seven days put Chill PVE for hard workers at #6,638, in the top 30% of all ranked servers.

How full does Chill PVE for hard workers get?

0 of 70 slots are filled on Chill PVE for hard workers right now. Seven-day check: 0 players on average. Peak reading: 2. Average at the busiest hour was 0 players, at 00:00 UTC over the last 48 hours.

Server

Which location does Chill PVE for hard workers run from?

Reading: location. Chill PVE for hard workers gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 104.192.227.10:28015.

What Rust version is Chill PVE for hard workers on?

Reading: Chill PVE for hard workers, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is performance on Chill PVE for hard workers within range?

Over the last 48 hours the average was 71 server fps; the floor was 53. Reading: 216,467 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 8,078 MB. Expect lag when fps falls and entities climb.

How reliable is Chill PVE for hard workers, and is it online now?

Check: connection. Chill PVE for hard workers is online at this moment. Check: restart. The uptime it reports puts the last restart about 6 days 7 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is Chill PVE for hard workers configured, and what rules are in force?

Reading the name gives no gather rate for Chill PVE for hard workers. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: other players are not fought. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Chill PVE for hard workers?

Check: map. Procedural, size 6,000, seed 3343399825, generated by the game on Chill PVE for hard workers. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto Chill PVE for hard workers?

Press F1 in Rust and enter client.connect 104.192.227.10:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp70,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp70
Max players 70 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.