RUST ZERG LIFEClan war room · live
Duomax 2
Deployment dossierOnline

The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |

NA 216.245.176.156:28025 checked 14m ago

2x duo biweekly wipes moddedoxide
Deploy
Zerg meter0%empty
0/20 troops
7-day average1
peak 5
Rank#3,750
top 17% · #664 in NA
Last wipe13d ago
biweekly schedule
Next wipe · H-hour12h
Thu 15 Oct, 18:05 UTC

Players

AveragePeak
0246807:0016:0001:0010:0019:0004:00

Hourly average and peak, UTC.

Server performance

02040608007:0016:0001:0010:0019:0004:00

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
11k2k3k4k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

Top 17% of all ranked servers, top 36% in NA, and #214 of the duo servers (top 50%). Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Thursday 15 October, 18:05 UTC, in 12h. Its biweekly schedule tag · low confidence

usual gap14 days
between real wipes
wipe-day peak9
players, last three wipes
crowd held0%
else halves by day 1

Coming wipes

12hThu 15 Oct, 18:05 UTC
14d 12hThu 29 Oct, 18:05 UTC
21d 12hThu 5 Nov, 19:00 UTCFW
28d 12hThu 12 Nov, 18:05 UTC
42d 12hThu 26 Nov, 18:05 UTC

The first 48 hours of its last wipes

Thu 1 OctThu 17 Sep
02.557.510+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 7, 9 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:05 UTC FW13d ago 7 – running 0
Thu 17 Sep, 18:09 UTC27d 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
Duomax 2
WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED NA · duo · 2x · weekly · 152 on average
289/350
Duomax 2
US Limitless 2x Monthly Solo/Duo|No BP Wipes|Noob Friendly NA · duo · 2x · monthly · 144 on average
136/200
Duomax 2
US RENEGADE 2x Monthly | Solo Duo | 50% Upkeep | No BP Wipe NA · duo · 2x · monthly · 28 on average
12/150
Duomax 2
US Rusty Rats 2x Monthly | Solo/Duo | 50% Upkeep | No BP Wipe NA · duo · 2x · monthly · 16 on average
9/200
Triomax 3
HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED NA · trio · 2x · biweekly · 11 on average
7/150
Duomax 2
US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just Wiped NA · duo · 2x · weekly · 7 on average
15/100

Quick answers

from the figures on this page

Map and rules

What is the setup on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | when it comes to rules and settings?

The name The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | tells you the gather rate: 2x. 2 players is the group cap (duo). survival is its mode, gather, build, raid: the regular game. Raiding and fighting other players are allowed. This one sits under Modded in the browser: the game is changed by plugins or settings. It runs plugins: Oxide. VAC is on, Valve's anti-cheat.

Which map is active on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

A published map file for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |'s custom map of size 4,000 is downloadable from this page.

Player count

What is the population like on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | has 0 of its 20 slots filled right now. The seven-day average is 1 players, with a peak of 5. The busiest time in the last 48 hours was 22:00 UTC, when it averaged 4 players.

What position does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | hold in the server rankings?

In North America, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is #664, and globally it is #3,750 for player hours over the last seven days, within the top 17% of all ranked servers. Among servers in the duo group, it sits at #214.

Lists and tags

What is the meaning of the tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

For the game's server browser, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp20 (Max players): Capacity: 20; ts2 (Group limit): Each team can have up to 2 players; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs167231 (Build): It runs build 167231; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): There's no region code here; ^b (Biweekly): A wipe comes every fortnight; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded category: the game is altered by plugins or settings; NA (North America): In the server browser this one sits under North America; rustmaps (Custom tag): The owner or a plugin set this tag; it's not part of standard Rust. The tags carry its players now, its queue and the time its world was made as well, and the top of this page displays them.

Which Rust Zerg Life filters and lists cover The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

2x Rust servers for clans and zergs, Duo Rust servers, listed straight, Modded Rust servers for clans and zergs and North American Rust servers: that is where you will find The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | among the Rust Zerg Life rankings. Under these filters it shows on the server list: 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 details

How reliable is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, and is it up?

Right now, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is online. The uptime figure it gives suggests it restarted around 18 hours ago. Over the last 7 full days, uptime was 100%: 168 hours up out of 168. Rust Zerg Life has been tracking it since 13 September 2026.

What is the performance like on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

Server fps held an average of 64 for the last 48 hours, with a minimum of 59. It reached a maximum of 102,959 entities, covering buildings, deployables and the rest of the world. Memory use peaked at 2,976 MB. What players experience as lag comes from low fps and a rising entity count.

Which Rust build does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | use?

On Windows, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | runs Rust network protocol 2634 and build 167231. Joining requires your game to be on the same protocol, which Steam updates automatically.

Where can you find The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

In North America, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lists itself with its NA tag. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 216.245.176.156:28025.

Wipe cycle

What can you expect on wipe day on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

The average peak for its recent wipes was 9 players. On the latest wipe, 9 hours after the wipe, the crowd hit its peak. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. Otherwise, it slipped below half by day 1.

How often does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe, and on what days?

The prediction follows its tag because not enough of The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |'s wipes are on record to confirm the schedule. Thursday 15 October at 18:05 UTC is when its next wipe is due. 13 days 11 hours ago is when its present world was created. Its tags show a wipe schedule of every two weeks.

Connect

What steps do I take to join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

Join by entering client.connect 216.245.176.156:28025 in the console (press F1 first). Or use Launch Rust on this page, which opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/J8y8ZTjK8y.

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,^b,NA,gmrust,cs167231,ts2,^o^z,rustmaps

Game

gmrust
Game mode Survival in the standard Rust mode.
mp20
Max players Capacity: 20.
ts2
Group limit Each team can have up to 2 players.
v2634
Protocol Protocol 2634—only players on that version can get in.
cs167231
Build It runs build 167231.
ptrak
Networking The network layer is RakNet, which is standard.
$r?
Region code There's no region code here.

Wipe schedule

^b
Biweekly A wipe comes every fortnight.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Modded category: the game is altered by plugins or settings.

Region

NA
North America In the server browser this one sits under North America.

Other

rustmaps
Custom tag The owner or a plugin set this tag; it's not part of 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.