Working its way up from the back of the class: #16,408 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 9,655 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 17h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll see [US] Chronic Condition listed in North America, tagged NA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 156.236.84.44:28065 is the address to use.
How reliable is [US] Chronic Condition, and is it up?
You cannot join now: [US] Chronic Condition is offline, last seen 27 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does [US] Chronic Condition sit?
The server [US] Chronic Condition is on Rust network protocol 2633 and build 165217 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does [US] Chronic Condition wipe its map?
The next wipe on [US] Chronic Condition is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 54 days 15 hours. The tags show a monthly wipe schedule.
Player numbers
Where does [US] Chronic Condition place in the wider field of Rust servers?
Over the last seven days, [US] Chronic Condition has #16,408 for player hours, in the top 69% of all ranked servers and #1,629 in North America.
What does the population on [US] Chronic Condition look like?
[US] Chronic Condition is offline at the moment; the last time it was seen was 27 days 11 hours ago.
Tags
How should you read the tags on [US] Chronic Condition?
The game's browser takes its cue from the tags [US] Chronic Condition has set: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Its slot count is 50; ts16 (Group limit): A team can hold 16 players at most; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): You will find it under North America in the browser. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature [US] Chronic Condition?
Rust Server Score lists that include [US] Chronic Condition: Modded Rust servers, graded and North America Rust servers, graded. These filters bring it up on the server 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.
Server rules
Which rules does [US] Chronic Condition enforce, and what are its settings?
Nothing in the name of [US] Chronic Condition states a gather rate. The limit for a group is 16 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
[US] Chronic Condition runs which map?
The game generates the procedural map on [US] Chronic Condition at size 4,250 with seed 1564901445. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto [US] Chronic Condition?
To connect, start Rust, press F1, and type client.connect 156.236.84.44:28065. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^m,^v,NA,gmvanilla,cs165217,ts16,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersIts slot count is 50.
ts16
Group limitA team can hold 16 players at most.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
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 standing (F); momentum is the one to work on (F).