RUST METRICSFlight deck · live data
Data live Servers11,799 Players79,295 Populated3,786 Fresh wipes 3 h103 Scan5 min
‹ All servers66.51.99.69:28065
Online Full Queue Fresh wipe Wipe due No query

[US] Chronic Condition

Online NA 66.51.99.69:28065 checked 9m ago

monthly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Wed 17:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 6 SERVER FPS

Server fps

48 h low 5 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 109,283 ×1000

Entities

48 h range 102,807–111,203 · memory 3,014 MB
1239 ET SINCE RESTART 06:33

Uptime

6 h 33 min since its last restart, at the last reading
7-day average0peak –
Rank#15,323top 69% · #1529 in NA
Last wipe26d agomonthly schedule
Next wipe7d 22hThu 5 Nov, 19:00 UTC FW
Memory3,014MBat the last reading
REC 1

Players

AveragePeak
0123421:0006:0015:0000:0009:0019:00

Hourly average and peak, UTC.

REC 2

Server performance

0246821:0006:0015:0000:0009:0019: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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct6 Oct12 Oct17 Oct23 Oct28 Oct

Top 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h. The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 22hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 22hFW

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 09:40 UTC26d 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.

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 schedule

What happens on [US] Chronic Condition when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does [US] Chronic Condition wipe, and when?

Once a month [US] Chronic Condition wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 26 days 10 hours ago. The tags state a wipe schedule of one wipe a month.

Tag meanings

Which tags does [US] Chronic Condition carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): The server holds 50 slots; ts16 (Group limit): You may team up with at most 16; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; NA (North America): North America is the browser category it sits in from [US] Chronic Condition. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does [US] Chronic Condition appear in Rust Metrics lists and filters?

Rust Metrics lists featuring [US] Chronic Condition: Modded Rust servers, checked live and North America: server readout. Reading: server list filters. It comes up under Region: North America; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Occupancy

Where does [US] Chronic Condition sit in the rankings?

Ranked by seven-day player hours, [US] Chronic Condition sits at #15,323 and #1,529 in North America, inside the top 69%.

What is the population on [US] Chronic Condition?

Current headcount on [US] Chronic Condition: 0 players, 50 slots available. Check: player average. 0 over the last seven days.

Server

What location is [US] Chronic Condition hosted in?

Its NA tag places [US] Chronic Condition in North America. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 66.51.99.69:28065.

What Rust version is [US] Chronic Condition on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [US] Chronic Condition. Check: protocol. To join, your game must match; Steam handles the update.

How does [US] Chronic Condition perform?

Check: fps. Average 5 server fps over the last 48 hours, low of 5. Within range. Check: entities. The peak was 111,203, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,426 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is [US] Chronic Condition up, and how often does it stay up?

Check: connection. [US] Chronic Condition is online at this moment. Check: restart. The uptime it reports puts the last restart about 6 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 1 October 2026.

Map and rules

What settings and rules apply on [US] Chronic Condition?

No gather rate appears in the name: [US] Chronic Condition. Check: group limit. Up to 16 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.

What map is [US] Chronic Condition on?

From seed 1564901445, the game generates the procedural map on [US] Chronic Condition. Its size is 4,250. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join [US] Chronic Condition?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,^v,NA,gmvanilla,cs168909,ts16,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp50
Max players The server holds 50 slots.
ts16
Group limit You may team up with at most 16.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

NA
North America North America is the browser category it sits in.

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.