RUST METRICSFlight deck · live data
Data live Servers11,636 Players40,778 Populated2,957 Fresh wipes 3 h88 Scan5 min
‹ All servers73.31.232.91:28015
Offline Full Queue Fresh wipe Wipe due No query

Candys Delicious House Rules

Offline 73.31.232.91:28015 checked 19d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 2 /10

Players now

20% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#12,118top 55%
Last wipe24d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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. 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 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

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

PLAN

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 gap6.8 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 3 OctWed 30 SepMon 21 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 14:06 UTC24d ago 2 – running 0
Wed 30 Sep, 16:31 UTC27d ago 2 – 2.9 days 2
Mon 21 Sep, 15:11 UTC36d ago 2 held half 9.1 days 2
Mon 14 Sep, 19:55 UTC43d ago 2 held half 6.8 days 2

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

Wipe timing

What happens on Candys Delicious House Rules when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does Candys Delicious House Rules wipe?

There is no next wipe to predict: Candys Delicious House Rules wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 24 days 11 hours ago the current world was made.

Tag meanings

How should you read the tags on Candys Delicious House Rules?

Tags published by Candys Delicious House Rules, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Game build reading: 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Candys Delicious House Rules?

Rust Metrics lists featuring Candys Delicious House Rules: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does Candys Delicious House Rules hold among Rust servers?

Player hours over seven days put Candys Delicious House Rules at #12,118, in the top 55% of all ranked servers.

What is the population on Candys Delicious House Rules?

Status for Candys Delicious House Rules: offline. Last seen 19 days 5 hours ago.

Operator and location

Where does Candys Delicious House Rules sit?

No region tag on Candys Delicious House Rules. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 73.31.232.91:28015.

What Rust version is Candys Delicious House Rules on?

Rust network protocol 2634 and build 167231 on Windows is the build Candys Delicious House Rules runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Candys Delicious House Rules up, and how often does it stay up?

Check: connection. Candys Delicious House Rules is offline at this moment. Last contact was 19 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What rules does Candys Delicious House Rules enforce, and what are its settings?

No gather rate appears in the name: Candys Delicious House Rules. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Candys Delicious House Rules?

The game generates a procedural map for Candys Delicious House Rules.

How to join

How can you get onto Candys Delicious House Rules?

Check: join. Open Rust, press F1, then enter client.connect 73.31.232.91:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Game build reading: 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the 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.