On the class lists: D (47), with population over 48 hours and no performance mark.
Players now1/ 205% full
7-day average3peak 11
Rank#1,804top 8% · #277 in NA
Last wipe13d agobiweekly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
14/ 100
F
A quiet classroom so far: 3 of 20 on average. Plenty of space to grow.
Standingrank on player hours
92/ 100
A
Well up the rankings: #1,804 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
96/ 100
A+
Runs smoothly: 58 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
40/ 100
F
Slipped a little: down 358 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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 8% of all ranked servers, top 15% in NA, and #122 of the duo servers (top 29%). Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
···F···
·······
···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 5 November, 19:00 UTC, in 7d 11h.
The force wipe · high confidence
usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak10players, last three wipes
crowd held0%else halves by day 4
Coming wipes
7d 11hThu 5 Nov, 19:00 UTCFW
14d 10hThu 12 Nov, 18:07 UTC
35d 11hThu 3 Dec, 19:00 UTCFW
42d 10hThu 10 Dec, 18:07 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 12, 7 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 18:07 UTC13d ago
12
–
running
2
Thu 1 Oct, 18:05 UTCFW27d ago
7
halved by day 7
14 days
0
Thu 17 Sep, 18:09 UTC41d ago
11
halved by day 1
14 days
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
Where in the world is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
The NA tag on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | puts it in North America. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 216.245.176.156:28025.
Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | up, and how steady is its uptime?
The server is up: The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is online now. About 19 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | smooth to play on?
It averaged 58 server fps over the last 48 hours, with a low of 46. Buildings, deployables and everything else in the world added up to as many as 113,832 entities. Up to 3,565 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/Duo | Raid Hours | Bi-Weekly | on?
Rust network protocol 2635 and build 168909 on Windows is what The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe its map?
Its wipe pattern: The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipes every 4 weeks on Thursday at 18:07 UTC. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 13 days 13 hours. Its tags give a wipe schedule of every two weeks.
What happens on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | when wipe day arrives?
Across its recent wipes, the busiest moments averaged 10 players. 7 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 4 in the wipes where it did not hold.
Player count
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | sit among Rust servers?
Over the last seven days, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | has #1,804 for player hours, in the top 8% of all ranked servers and #277 in North America. It comes #122 among servers in the duo group.
What does the population on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | look like?
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is showing 1 players right now, with 20 slots in total. It peaked at 11 and averaged 3 players over the last seven days. Over the last 48 hours, the peak hour was 01:00 UTC, averaging 6 players.
Tags
What is meant by the tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
The game's browser takes its cue from the tags The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | has set: gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): 20 slots are available; ts2 (Group limit): No team may go above 2; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; NA (North America): You will find it under North America in the browser; rustmaps (Custom tag): The owner or a plugin created this tag, so it is not standard Rust. 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 The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear in the Rust Server Score lists and filters?
Rust Server Score lists that include The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: 2x Rust servers, graded, Duo servers, marked like a report, Modded 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: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
Server rules
How is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | set up, and what rules does it keep?
The name of The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | points to a 2x gather rate. You can have up to 2 players in a group (duo). You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | uses?
The map on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is custom at size 4,000, and because the file is published you can download it from this page.
Connecting
How do you get onto The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Enter client.connect 216.245.176.156:28025 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/J8y8ZTjK8y.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,^b,NA,gmrust,cs168909,ts2,^o^z,rustmaps
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max players20 slots are available.
ts2
Group limitNo team may go above 2.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
Other
rustmaps
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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 fair term, with more to come. Strongest in uptime (A+); wipes are the one to work on (F).