DWG RG-S1804Server sheetchecked 15m ago
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |
Online NA 216.245.176.156:28025 checked 15m ago
Players
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
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.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence
Coming wipes
- 7d 11hThu 5 Nov, 19:00 UTCFW
- 14d 10hThu 12 Nov, 18:07 UTC
- 35d 11hThu 3 Dec, 19:00 UTCFW
- 42d 10hThu 10 Dec, 18:07 UTC
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
| 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
Quick answers
Server details
How reliable is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, and is it online now?
Right now, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is recorded as online. About 19 hours ago is when it last restarted, measured from the uptime it reports. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | stable in the figures recorded?
58 server fps on average over the last 48 hours, and never under 46. Counted at its highest: 113,832 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,565 MB. What players feel as lag is low fps together with a climbing entity count.
What location is recorded for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
With its NA tag, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lists itself in North America. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 216.245.176.156:28025 is its address.
What Rust version is recorded for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
On Windows, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.
Population
How many players are plotted on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Current player count on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: 1, of 20 slots. The seven-day mean is 3 players; the peak over the same period is 11. The 48-hour peak falls at 01:00 UTC, averaging 6 players.
In the rankings, which position does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | hold?
The same seven-day player-hour count places The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | at #277 within North America, #1,804 across all ranked servers and in the top 8% of them. Ranked #122 among duo servers.
Schedules
What happens on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | on the day of a wipe?
An average of 10 players was recorded at the busiest point of its recent wipes. 7 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 4.
What wipe schedule has been recorded for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Wipes at The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | take place every 4 weeks on Thursday at 18:07 UTC. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 13 days 13 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.
Rules and settings
Which settings does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run, and what rules?
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | takes its gather rate from its name: 2x. A group tops out at 2 players (duo). It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.
On which map is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | played?
Size 4,000, custom, on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: the map file is published and can be downloaded from this page.
Tags
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | are: Servers with a 2x gather rate, Duo Rust servers, Modded Rust servers and Rust server list: North America. It is returned by these filters 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.
Which meaning is attached to each tag on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
gmrust (Game mode): Standard survival, as Rust plays; mp20 (Max players): The slot count is 20; ts2 (Group limit): Teams hold no more than 2; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; NA (North America): In the server browser it appears under North America; rustmaps (Custom tag): Set by the owner or a plugin, not by standard Rust are the tags The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Joining the server
How is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | joined?
Connect with client.connect 216.245.176.156:28025: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://discord.com/invite/J8y8ZTjK8y.
Server tags
Published as mp20,ptrak,$r?,v2635,^b,NA,gmrust,cs168909,ts2,^o^z,rustmaps
Game
gmrust
mp20
ts2
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
^z
Region
NA
Other
rustmaps
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.