Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO V SRV11,711online PAX58,911playing OCC3,347with players WIPED 3H176
MODModded traffic
Callsign

WRK1793=

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

Online NA 216.245.176.156:28025 checked 12m ago

2x duo biweekly wipes moddedoxide
Clearance · join
Players now 0/ 20 0% full
7-day average3peak 11
Rank#1,793top 8% · #276 in NA
Last wipe13d agobiweekly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
0246811:0020:0005:0014:0000:0009:00

Hourly average and peak, UTC.

Server performance

02040608011:0020:0005:0014:0000:0009: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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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.

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h.

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

  1. 7d 8hThu 5 Nov, 19:00 UTCFW
  2. 14d 7hThu 12 Nov, 18:07 UTC
  3. 35d 8hThu 3 Dec, 19:00 UTCFW
  4. 42d 7hThu 10 Dec, 18:07 UTC

The first 48 hours of its last wipes

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

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

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign WRB015NA · duo · 2x · weekly · 143 on average WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED
    Players 91/200
  2. 02MOD
    Callsign LMT015NA · duo · 2x · monthly · 57 on average US Limitless 2x Monthly Solo/Duo|No BP Wipes|Noob Friendly
    Players 25/200
  3. 03MOD
    Callsign RNG016NA · duo · 2x · monthly · 25 on average US RENEGADE 2x Monthly | Solo Duo | 50% Upkeep | No BP Wipe
    Players 9/150
  4. 04MOD
    Callsign HLL010NA · trio · 2x · biweekly · 10 on average HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED
    Players 5/150
  5. 05MOD
    Callsign LMT015NA · duo · 2x · weekly · 8 on average US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just Wiped
    Players 4/100
  6. 06MOD
    Callsign RST013NA · duo · 2x · monthly · 5 on average US Rusty Rats 2x Monthly | Solo/Duo | 50% Upkeep | No BP Wipe
    Players 2/200
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear in Rust Tracker lists and filters?

2x Rust servers, tracked live, Duo servers: group limit 2, Modded servers, tracked live and North America: live server tracking — the Rust Tracker lists that include The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. On the server list, these filters bring it up: 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 |?

Listed for the server browser to read, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp20 (Max players): Capacity: 20 slots; ts2 (Group limit): Teams are capped at 2; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): A wipe every fortnight; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings; NA (North America): In the server browser it is listed under North America; rustmaps (Custom tag): Set by the owner or a plugin; not a standard Rust tag. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

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

Recent wipes averaged a peak of 10 players. 7 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The fall below half came by day 4 where it did not hold.

On what schedule does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe?

At The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | the wipes follow a every 4 weeks on Thursday at 18:07 UTC rhythm. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. This world has been running 13 days 16 hours. A two-weekly wipe schedule is published in its tags.

Location and Status

Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | up, and how does its uptime hold?

Tracking shows The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | online as of now. The uptime it reports puts the last restart about 22 hours ago. Uptime stood at 99% for the last 7 full days, 167 of 168 hours online. Rust Tracker logged it first on 13 September 2026.

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

Rust network protocol 2635 and build 168909 is the build on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |; the platform is Windows. The same protocol is required to join, and Steam updates it for you.

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

Server fps held an average of 57 across the last 48 hours, never below 46. Peak entity count: 113,832, covering buildings, deployables and all else in the world. It drew as much as 3,565 MB of memory. Players feel lag when fps drops and the entity count climbs.

What location is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | hosted in?

Listed in North America under NA: that is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | by its own tags. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 216.245.176.156:28025.

Player Count

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

Slots 20; players on board 0: that is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | now. Peak of 11 in the last seven days, average 3 players. At 01:00 UTC it drew its highest average of the last 48 hours: 6 players.

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

Seven-day player hours: #1,793 overall for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, top 8% of ranked servers, #276 in North America. Within the duo group it sits at #122.

Map and Rules

Which settings and rules are confirmed on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

2x gather is what The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | runs, going by its name. A limit of 2 players applies per group (duo). It runs survival, gather, build and raid: the standard game. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.

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

Custom map, size 4,000, on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: the file is published for download from this page.

Connect

Which steps join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?

To connect: start Rust, press F1, enter client.connect 216.245.176.156:28025 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://discord.com/invite/J8y8ZTjK8y.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp20
Max players Capacity: 20 slots.
ts2
Group limit Teams are capped at 2.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.

Region

NA
North America In the server browser it is listed under North America.

Other

rustmaps
Custom tag Set by the owner or a plugin; not a standard Rust tag.

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.