On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,373top 69% · #1531 in NA
Last wipe26d agomonthly schedule
Next wipe7d 23hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,373 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
9/ 100
F
Needs to work on its frame rate: 5 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 200 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 1 Oct. 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
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
7d 23hThu 5 Nov, 19:00 UTCFW
35d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The NA tag on [US] Chronic Condition puts it in North America. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 66.51.99.69:28065 is the address to use.
How dependable is [US] Chronic Condition, and is it online at the moment?
You can join now: [US] Chronic Condition is online. About 6 hours ago, it restarted, based on the uptime it reports. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 1 October 2026.
Is [US] Chronic Condition smooth to play on?
It averaged 5 server fps over the last 48 hours, with a low of 5. Up to 111,203 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,426 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is [US] Chronic Condition running?
Rust network protocol 2635 and build 168909 on Linux is what [US] Chronic Condition runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does [US] Chronic Condition reset?
[US] Chronic Condition wipes with the force wipe and at no other time. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 26 days 9 hours. The tags show a monthly wipe schedule.
What happens on [US] Chronic Condition when wipe day arrives?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Player numbers
Where does [US] Chronic Condition place in the wider field of Rust servers?
Over the last seven days, [US] Chronic Condition has #15,373 for player hours, in the top 69% of all ranked servers and #1,531 in North America.
How many players does [US] Chronic Condition usually have?
With 50 slots available, [US] Chronic Condition currently has 0 players. A seven-day average of 0 players applies here.
Tags
What is meant by the tags on [US] Chronic Condition?
The game's browser takes its cue from the tags [US] Chronic Condition has set: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): The server holds 50 slots; ts16 (Group limit): A team can hold 16 players at most; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^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): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): In the server browser it appears under North America. 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. It shows under the following filters 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
How is [US] Chronic Condition set up, and what rules does it keep?
You will find no gather rate in the name of [US] Chronic Condition. You can play in groups of up to 16 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. 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?
A procedural map of size 4,250 and seed 1564901445, generated by the game, is what [US] Chronic Condition runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to [US] Chronic Condition?
To connect, start Rust, press F1, and type client.connect 66.51.99.69:28065. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,^v,NA,gmvanilla,cs168909,ts16,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersThe server holds 50 slots.
ts16
Group limitA team can hold 16 players at most.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
NA
North AmericaIn the server browser it appears 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).