The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |
Online NA 216.245.176.156:28025 checked 13m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 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.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 3h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 14d 2h | Thu 12 Nov, 18:07 UTC | its own |
| 35d 3h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 42d 2h | Thu 10 Dec, 18:07 UTC | its own |
The first 48 hours of its last wipes
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 UTC FW27d 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
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED | NA · duo · 2x · weekly · 144 on average | 151 / 200 |
| US Limitless 2x Monthly Solo/Duo|No BP Wipes|Noob Friendly | NA · duo · 2x · monthly · 56 on average | 34 / 200 |
| US RENEGADE 2x Monthly | Solo Duo | 50% Upkeep | No BP Wipe | NA · duo · 2x · monthly · 25 on average | 12 / 150 |
| HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED | NA · trio · 2x · biweekly · 11 on average | 5 / 150 |
| US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just Wiped | NA · duo · 2x · weekly · 8 on average | 2 / 100 |
| US Rusty Rats 2x Monthly | Solo/Duo | 50% Upkeep | No BP Wipe | NA · duo · 2x · monthly · 5 on average | 5 / 200 |
Quick answers
from the figures on this pageWipe data
On what cycle does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe?
The wipe rhythm of The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is every 4 weeks on Thursday at 18:07 UTC. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The world now in play was created 13 days 21 hours ago. Its tags publish a wipe schedule of every two weeks.
Wipe day on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: what should you expect?
Recent wipes averaged a busiest count of 10 players. 7 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. The fall below half arrived by day 4 when it didn't hold.
Server
In which region does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | sit?
The NA tag on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lists it in North America. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 216.245.176.156:28025.
Which Rust version is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | on?
Rust network protocol 2635 and build 168909 on Windows is the setup for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. Your game must match the protocol to join, and Steam applies that update.
What uptime does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | show, and is it up?
As of the latest refresh, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is online. Its reported uptime indicates a restart roughly 3 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. The first sighting of it by Rust Server Analytics was on 13 September 2026.
Is performance on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | stable?
Server fps averaged 58 over the last 48 hours, with a floor of 48. Entity count reached 113,832, covering buildings, deployables and the rest of the world. Memory use reached 3,565 MB at peak. A climbing entity count and low fps are the lag players perceive.
Tags
Which meanings do the tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | carry?
The game's server browser reads the tags The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | publishes: gmrust (Game mode): Survival in the standard Rust format; mp20 (Max players): Player slots: 20; ts2 (Group limit): Teams hold no more than 2; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^b (Biweekly): A two-week wipe cycle; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): The Modded section, because plugins or settings modify play; NA (North America): North America is the region it appears under in the browser; rustmaps (Custom tag): A custom tag, set by the owner or a plugin, outside the standard set. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | fits are: Rust servers with a 2x gather rate, Duo Rust servers, Modded Rust servers: live data and North America Rust servers. On the server list, the filters that return it are: 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.
Population
Against other Rust servers, how does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | compare?
For player hours over the last seven days, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | places #1,799 globally and #276 in North America, in the top 8% of all ranked servers. Within the duo segment, its position is #122.
What is the population of The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Of 20 slots, 1 are filled on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | at this refresh. Seven-day figures: an average of 3 players and a peak of 11. Across the last 48 hours, 01:00 UTC shows the highest average: 6 players.
Settings
How is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | configured, and what rules apply?
Gather at 2x on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, according to the server name. A maximum of 2 players per group is set (duo). survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. VAC, Valve's anti-cheat, is enabled.
The map on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: which one is it?
A custom map of size 4,000 is used on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |; its file is published and downloadable here.
How to join
How can a player join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
In the Rust console (F1), enter client.connect 216.245.176.156:28025. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://discord.com/invite/J8y8ZTjK8y is its website.