The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |
Online NA 216.245.176.156:28025 checked 12m ago
Server instruments
last reading Fri 04:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 48 · below 20 is lag, below 10 is badEntities
48 h range 105,608–113,832 · memory 2,989 MBUptime
17 h 56 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 9% of all ranked servers, top 16% in NA, and #137 of the duo servers (top 32%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 6d 12h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC6d 12hFW
- WPT 2Thu 12 Nov, 18:07 UTC13d 11h
- WPT 3Thu 3 Dec, 19:00 UTC34d 12hFW
- WPT 4Thu 10 Dec, 18:07 UTC41d 11h
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 UTC14d ago | 12 | – | running | 2 |
| Thu 1 Oct, 18:05 UTC FW28d ago | 7 | halved by day 7 | 14 days | 0 |
| Thu 17 Sep, 18:09 UTC42d 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- 94/200
- 38/200
- 17/150
- 17/150
- 2/100
- 4/20
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
At their busiest, its recent wipes drew 10 players on average. After the latest wipe, numbers topped out at 7 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 4 when it didn't.
How often does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe, and when?
The wipe rhythm of The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is every 4 weeks on Thursday at 18:07 UTC. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 14 days 12 hours ago. The tags carry an every-two-weeks wipe schedule.
Tags
How should you read the tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Tags published by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): 20 slots in total; ts2 (Group limit): Team cap: 2; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): The server browser files it under North America; rustmaps (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear in Rust Metrics lists and filters?
These Rust Metrics lists carry The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: 2x Rust servers, checked live, Duo Rust servers, Modded Rust servers, checked live and North America: server readout. These filters 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; Gather rate: 2x.
Player count
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | sit in the rankings?
Ranked by seven-day player hours, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | sits at #1,944 and #296 in North America, inside the top 9%. Check: group rank. #137 among duo servers.
How full does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | get?
Current headcount on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: 0 players, 20 slots available. Seven-day check: 2 players on average. Peak reading: 11. Check: 48-hour peak. 01:00 UTC, 6 players on average.
Operator and location
Which location does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run from?
Its NA tag places The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 216.245.176.156:28025.
What Rust version is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. Matching protocol is required to join. Let Steam update your game.
How does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | perform?
Reading: 59 server fps on average across the last 48 hours. It never dropped below 48. Check: entities. The peak was 113,832, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,565 MB. What players call lag comes from low fps and an entity count on the rise.
Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | up, and how often does it stay up?
Reading: online. The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | answers right now. By its reported uptime, the last restart was roughly 17 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | configured, and what rules are in force?
Gather rate check: 2x. That comes from the name The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. The group cap is 2 players, read as duo. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | on?
Size 4,000, custom map, on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. The file is published and downloadable here.
Join
What do you do to join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Press F1 in Rust and enter client.connect 216.245.176.156:28025. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://discord.com/invite/J8y8ZTjK8y is where its website sits.