On the class lists: C− (57), with population over 48 hours and no performance mark.
Players now1/ 205% full
7-day average7peak 29
Rank#1,183top 5% · #176 in NA
Last wipe5d agoweekly schedule
Next wipe1d 21hThu 29 Oct, 18:24 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
34/ 100
F
A quiet classroom so far: 7 of 20 on average. Plenty of space to grow.
Standingrank on player hours
95/ 100
A+
Well up the rankings: #1,183 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
92/ 100
A
Mostly smooth: 55 server fps on average.
Wipeskeeping the crowd after a wipe
20/ 100
F
Needs to keep more players after wipe day: 20% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 24 places this week.
A steady term.
Strongest in uptime (A+); wipes are 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 5% of all ranked servers, top 9% in NA, and #54 of the solo servers (top 24%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···F···
···W···
···W···
···W···
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Thursday 29 October, 18:24 UTC, in 1d 21h.
Every Thursday at 18:24 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak26players, last three wipes
crowd held20%else halves by day 4.5
Coming wipes
1d 21hThu 29 Oct, 18:24 UTC
8d 21hThu 5 Nov, 19:00 UTCFW
15d 21hThu 12 Nov, 18:24 UTC
22d 21hThu 19 Nov, 18:24 UTC
29d 21hThu 26 Nov, 18:24 UTC
36d 21hThu 3 Dec, 19:00 UTCFW
43d 21hThu 10 Dec, 18:24 UTC
The first 48 hours of its last wipes
Thu 22 OctThu 15 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 29, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 18:24 UTC5d ago
29
–
running
6
Thu 15 Oct, 18:02 UTC12d ago
24
halved by day 5
7 days
1
Thu 8 Oct, 18:01 UTC19d ago
24
halved by day 5
7 days
5
Thu 1 Oct, 18:04 UTCFW26d ago
26
halved by day 4
7 days
1
Thu 24 Sep, 18:02 UTC33d ago
23
✓ held half
7 days
2
Thu 17 Sep, 18:07 UTC40d ago
24
halved by day 3
7 days
3
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
Where in the world is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
You'll see The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | 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. 104.129.132.49:28129 is the address to use.
How dependable is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, and is it online at the moment?
Right now, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | is online. According to its reported uptime, the last restart was about 9 hours ago. It was up 97% of the time over the last 7 full days, 163 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
How well does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | run?
It averaged 55 server fps over the last 48 hours, with a low of 5. At its peak, it held 127,826 entities, including buildings, deployables and all else in the world. Up to 4,081 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | on?
Rust network protocol 2635 and build 168909 on Linux is what The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | wipe, and how often?
Wipes come every Thursday at 18:24 UTC on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. Thursday 29 October at 18:24 UTC is the date set for its next wipe. It has been running its current world for 5 days 2 hours. The tags carry a weekly wipe schedule.
What should you expect from wipe day on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Across its recent wipes, the busiest moments averaged 26 players. Peak numbers came 8 hours into the latest wipe. Half the peak held until the next wipe in 20% of its recent wipes. The crowd dropped below half by day 4.5 in the wipes where it did not hold.
Player numbers
Where does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | sit among Rust servers?
Over the last seven days, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | has #1,183 for player hours, in the top 5% of all ranked servers and #176 in North America. It comes #54 among servers in the solo group.
How many players does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | usually have?
With 20 slots available, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | currently has 1 players. It peaked at 29 and averaged 7 players over the last seven days. The highest average in the last 48 hours came at 22:00 UTC, with 10 players.
Lists and filters
What do The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |'s tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): 20 slots are available; ts1 (Group limit): No team may go above 1; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^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): The server browser lists it under North America; rustmaps (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | appear in the Rust Server Score lists and filters?
These Rust Server Score lists count The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | among them: 2x Rust servers, graded, Modded Rust servers, graded, Solo Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Map and rules
What settings and rules apply on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The name of The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | points to a 2x gather rate. This is a solo-only server, so teams cannot form. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The map on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | is custom at size 4,000, and because the file is published you can download it from this page.
Getting in
How should you connect to The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
To connect, start Rust, press F1, and type client.connect 104.129.132.49:28129. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/J8y8ZTjK8y.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,^w,NA,gmrust,cs168909,ts1,rustmaps,^o^z,rustmaps
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max players20 slots are available.
ts1
Group limitNo team may go above 1.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
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 AmericaThe server browser lists it under North America.
Other
rustmaps
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 steady term. Strongest in uptime (A+); wipes are the one to work on (F).