On the class lists: C (64), with population over 48 hours and no performance mark.
Players now0/ 1200% full
7-day average0peak 3
Rank#5,458top 24%
Last wipe27d agono schedule published
Next wipe7d 1hThu 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 120 on average. Plenty of space to grow.
Standingrank on player hours
76/ 100
B
Holds a respectable place: #5,458 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
13/ 100
F
Needs to work on its frame rate: 8 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
82/ 100
B+
Climbing fast: up 3,468 places this week.
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
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 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 24% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
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 1h.
The force wipe · high confidence
wipe-day peak3players, last three wipes
Coming wipes
7d 1hThu 5 Nov, 19:00 UTCFW
35d 1hThu 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 3, 9 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 19:09 UTCFW27d ago
3
–
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
No region is published for Chicago Rust. Rust Server Score takes the server's word for its location and does not trace the hardware. 104.129.132.53:28259 is the address to use.
How reliable is Chicago Rust, and is it up?
You can join now: Chicago Rust is online. About 5 days 12 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
How well does Chicago Rust run?
It never fell below 5 server fps in the last 48 hours, averaging 8. At its peak, it held 107,011 entities, including buildings, deployables and all else in the world. Memory use reached up to 5,444 MB. When fps is low and entities climb, that is lag to players.
What Rust version is Chicago Rust on?
Rust network protocol 2635 and build 168909 on Linux is what Chicago Rust runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Chicago Rust reset?
Once a month, Chicago Rust wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 27 days 22 hours.
What should you expect from wipe day on Chicago Rust?
Recent wipes have peaked at 3 players on average. Peak numbers came 9 hours into the latest wipe.
Player numbers
Where does Chicago Rust sit among Rust servers?
Over the last seven days, Chicago Rust has #5,458 for player hours, in the top 24% of all ranked servers.
How many players does Chicago Rust usually have?
Right now, 0 players are on Chicago Rust, which has 120 slots. Averaging 0 players over seven days, it peaked at 3. Over the last 48 hours, the peak hour was 03:00 UTC, averaging 1 players.
Tags and filters
What do Chicago Rust's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp120 (Max players): The server holds 120 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^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 are the tags Chicago Rust publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Chicago Rust appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Chicago Rust among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does Chicago Rust enforce, and what are its settings?
You will find no gather rate in the name of Chicago Rust. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in 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. VAC, Valve's anti-cheat, is enabled.
Chicago Rust runs which map?
Chicago Rust runs a game-generated procedural map at size 4,300, seed 637000580. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join Chicago Rust?
To connect, start Rust, press F1, and type client.connect 104.129.132.53:28259. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp120,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp120
Max playersThe server holds 120 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.
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).