Rust HeatmapInfrared · players
IR live Players32,155 Servers11,637 Warm2,791 Fresh wipes · 3h71 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–50° · slots

[US] Chronic Condition

Online NA 66.51.99.69:28065 checked 10m ago

monthly wipes vanillamoddedoxide
Sp1 · players now 0/ 50
0% full
Li1 · players, the last 48 hours · hourly average, UTC
Tue 05:00flare: a wipe in that hourThu 03:00
0
7-day average
peak –
#15,349
rank
top 69% · #1513 in NA
26d ago
last wipe
monthly schedule
7d 14h
next wipe
Thu 5 Nov, 19:00 UTC FW
UTC checked 10m ago

Li2Players

AveragePeak
0123405:0014:0023:0008:0017:0003:00

Hourly average and peak, UTC.

Li3Server performance

0246805:0014:0023:0008:0017:0003: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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct7 Oct12 Oct18 Oct23 Oct29 Oct

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

Bx1Wipe schedule

force wipes only

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

0
wipe-day peak
players, last three wipes

Coming wipes

7d 14h
Thu 5 Nov, 19:00 UTC
FW
35d 14h
Thu 3 Dec, 19:00 UTC
FW

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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
[NA] Willjum's Casual Solo/Duo Monthly
NA · groups of 8+ · monthly · 15 on average
13 / 175
Hempville 420 No Kos Low Decay / Limited PvP
NA · groups of 8+ · monthly · 7 on average
7 / 90
Made in Quebec & France! QC FR EN (Website 9 Languages)
NA · groups of 8+ · monthly · 4 on average
3 / 1000
Testing Grounds
NA · groups of 8+ · monthly · 2 on average
1 / 15
Apocrypha-Linux | PvE | PvP
NA · groups of 20+ · monthly · 1 on average
3 / 50
[US] Exile PvE | Noob Friendly | Raidable Bases | Skill Tree |
NA · groups of 8+ · monthly · 1 on average
0 / 50

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on [US] Chronic Condition?

The average peak across its recent wipes is 0 players. The crowd on the latest wipe reached its peak 0 hours in.

What is the wipe schedule on [US] Chronic Condition?

A single monthly wipe, the force wipe, is all [US] Chronic Condition runs. On Thursday 5 November at 19:00 UTC the force wipe comes, and that is its next wipe, as for every Rust server. The world it runs now dates from 26 days 19 hours ago. The tags list one wipe a month.

Population

How busy is [US] Chronic Condition?

[US] Chronic Condition currently has 0 of its 50 slots filled. The average across the last seven days is 0 players.

How does [US] Chronic Condition rank against other Rust servers?

Top 69% of ranked servers and #1,513 in North America: that is [US] Chronic Condition at #15,349 for player hours over seven days.

Map and rules

Which map does [US] Chronic Condition run?

A procedural map of size 4,250 with seed 1564901445, generated by the game, runs on [US] Chronic Condition. You can look at the map on RustMaps from this page: the same size and seed give the same map.

What are the rules and settings on [US] Chronic Condition?

The name [US] Chronic Condition does not specify a gather rate. A maximum of 16 players is allowed per group. The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins run on this server. Its own label is vanilla: unchanged rates, kits and rules: the game in Facepunch's own form. Anti-cheat: Valve's VAC is on.

Server details

Which version of Rust does [US] Chronic Condition run?

Rust network protocol 2635 and build 168909 on Linux is what [US] Chronic Condition runs. Your game must run the same protocol to join, and Steam takes care of updating it.

Is [US] Chronic Condition online, and how reliable is it?

The server is up at the moment: [US] Chronic Condition is online. The uptime it reports puts the last restart at about 17 hours ago. It was up 167 of 168 hours across the last 7 full days, or 99% of the time. The first record of it on Rust Heatmap is 1 October 2026.

Where is [US] Chronic Condition located?

With its NA tag, [US] Chronic Condition lists itself in North America. Rust Heatmap shows the location a server states. It does not look up the machine's location. To connect, use 66.51.99.69:28065.

Does [US] Chronic Condition run smoothly?

Average server fps over the last 48 hours was 5; it never dropped below 5. Buildings, deployables and the rest of the world came to as much as 111,195 entities. At its peak it held 3,426 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.

Tags

Which Rust Heatmap lists and filters include [US] Chronic Condition?

These Rust Heatmap lists include [US] Chronic Condition: Modded Rust servers, by live population and North America server heatmap. These are the filters that return it on the list: 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.

What do the server tags on [US] Chronic Condition mean?

gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): The slot count is 50; ts16 (Group limit): Teams cap at 16; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): The game build here is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^v (Vanilla): Unchanged rates, kits and rules: the game in Facepunch's own form; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game; NA (North America): In the server browser it sits under North America are the tags [US] Chronic Condition publishes, and the server browser reads them. The top of this page also shows the tags for players now, the queue and when the world was made.

Connect

How do I join [US] Chronic Condition?

To join by console, open it with F1 in Rust and enter client.connect 66.51.99.69:28065. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players The slot count is 50.
ts16
Group limit Teams cap at 16.
v2635
Protocol The server runs game protocol 2635, so your game has to match it.
cs168909
Build The game build here is 168909.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code A region code is not set.

Wipe schedule

^m
Monthly The wipe cycle is monthly and follows Facepunch's force wipe.

Difficulty

^v
Vanilla Unchanged rates, kits and rules: the game in Facepunch's own form.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Listed as Modded, since settings or plugins change the game.

Region

NA
North America In the server browser it sits under North America.

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.