Top Rust ServersObservatory · live
Live Servers11,467 Players39,096 Populated3,035 Fresh wipes · 3h89 Scanevery 5 min

RS-3788Modded server

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

Online NA 216.245.176.156:28025 checked 9m ago

2x duo biweekly wipes moddedoxide
Connect
Players now
2/ 20
10% full
7-day average
1
peak 5
Rank
#3,788
top 17% · #673 in NA
Last wipe
13d ago
biweekly schedule
Next wipe
T− 15h
Thu 15 Oct, 18:05 UTC
Light curve

Players

AveragePeak
0246803:0012:0021:0007:0016:0001:00

Hourly average and peak, UTC.

Systems telemetry

Server performance

02040608003:0012:0021:0007:0016:0001: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.

Standing

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 #217 of the duo servers (top 50%). Ranked on player hours over the last seven days.

Orbit

Wipe schedule

from its schedule tag

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

usual gap14 daysbetween real wipes
wipe-day peak9players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. T− 15hThu 15 Oct, 18:05 UTC
  2. T− 14d 15hThu 29 Oct, 18:05 UTC
  3. T− 21d 16hThu 5 Nov, 19:00 UTCFW
  4. T− 28d 15hThu 12 Nov, 18:05 UTC
  5. T− 42d 15hThu 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.

Record

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.

Nearby objects

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Readouts in words

Quick answers

From the figures on this page.

Player activity

How many players are usually on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is showing 2 players on 20 slots right now. A seven-day average of 1 players was reached, peaking at 5. At 22:00 UTC it was busiest in the last 48 hours, averaging 4 players.

Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | sit in the rankings?

In North America, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is #673 on seven-day player hours, with #3,788 overall and a top 17% position among ranked servers. In the duo category, it ranks #217.

Server tags and lists

Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear among the Top Rust Servers lists and filters?

These Top Rust Servers lists include The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: Rust servers with 2x gather rate, Duo-limited Rust servers, ranked by live players, Top modded Rust servers and North American Rust servers. These are the filters that bring it up 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.

How should you read the tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

Published by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | for the game's server browser to read: gmrust (Game mode): Survival follows the standard Rust ruleset; mp20 (Max players): Player slots: 20; ts2 (Group limit): The team limit is 2; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs167231 (Build): The game build is 167231; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): No region code is assigned; ^b (Biweekly): This server wipes on a two-week cycle; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, so it is listed as Modded; NA (North America): The server browser lists it under North America; rustmaps (Custom tag): A non-standard tag, added by the owner or a plugin. Shown at the top of this page, and also in the tags: its players now, its queue, and the time its world was made.

Rules, settings, and map

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

A custom map of size 4,000 is in use on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, with the map file published and downloadable from this page.

What does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run for rules and settings?

The name The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | includes a 2x gather rate. Up to 2 players are allowed per group (duo). survival is the game mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are in use. The server runs with VAC on.

About the server

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

The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | uses Rust network protocol 2634 and build 167231 with Windows as its system. Joining requires matching protocols, and Steam updates your game automatically.

Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lag-free?

Its average server fps over the last 48 hours was 64, with a low of 51. Its entity count reached 102,959, including buildings, deployables and all other objects. At its highest, it consumed 2,976 MB of memory. A climbing entity count and low fps are the source of the lag players feel.

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

The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | uses its NA tag to list itself in North America. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 216.245.176.156:28025.

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

Right now, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is up and running. Going by its reported uptime, it restarted about 15 hours ago. It spent 168 of the last 168 hours online across 7 days, giving 100% uptime. It was first observed by Top Rust Servers on 13 September 2026.

Wipe schedule

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

The average busiest count over recent wipes is 9 players. The latest wipe saw its highest player count 9 hours in. The crowd kept above half its peak until the next wipe in 0% of recent wipes. When the peak was not held, numbers fell below half by day 1.

How often does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe?

Its tag guides the prediction because the record holds too few wipes to confirm The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |'s schedule. The upcoming wipe is set for Thursday 15 October at 18:05 UTC. The present world has been live since 13 days 8 hours ago. Its tags list a wipe schedule of every two weeks.

How to join

What is the process to join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

To connect manually, open the console with F1 and type client.connect 216.245.176.156:28025. Or click Launch Rust on this page to open Rust through Steam and connect directly. For its site, go to https://discord.com/invite/J8y8ZTjK8y.

Spectrum

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 follows the standard Rust ruleset.
mp20
Max players Player slots: 20.
ts2
Group limit The team limit is 2.
v2634
Protocol This server runs protocol 2634; match it to connect.
cs167231
Build The game build is 167231.
ptrak
Networking This uses RakNet, Rust's default network layer.
$r?
Region code No region code is assigned.

Wipe schedule

^b
Biweekly This server wipes on a two-week cycle.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded The game is changed by plugins or settings, so it is listed as Modded.

Region

NA
North America The server browser lists it under North America.

Other

rustmaps
Custom tag A non-standard tag, added by the owner or a plugin.

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.