DWG RG-S1174Server sheetchecked 6m ago
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |
Online NA 104.129.132.49:28129 checked 6m 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 5% of all ranked servers, top 9% in NA, and #52 of the solo servers (top 24%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 29 October, 18:24 UTC, in 1d 23h. Every Thursday at 18:24 UTC · high confidence
Coming wipes
- 1d 23hThu 29 Oct, 18:24 UTC
- 8d 23hThu 5 Nov, 19:00 UTCFW
- 15d 23hThu 12 Nov, 18:24 UTC
- 22d 23hThu 19 Nov, 18:24 UTC
- 29d 23hThu 26 Nov, 18:24 UTC
- 36d 23hThu 3 Dec, 19:00 UTCFW
- 43d 23hThu 10 Dec, 18:24 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 29, 8 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 18:24 UTC5d ago | 29 | – | running | 6 |
| Thu 15 Oct, 18:02 UTC12d ago | 24 | halved by day 5 | 7 days | 1 |
| Thu 8 Oct, 18:01 UTC19d ago | 24 | halved by day 5 | 7 days | 5 |
| Thu 1 Oct, 18:04 UTC FW26d ago | 26 | halved by day 4 | 7 days | 1 |
| Thu 24 Sep, 18:02 UTC33d ago | 23 | held half | 7 days | 2 |
| Thu 17 Sep, 18:07 UTC40d ago | 24 | halved by day 3 | 7 days | 3 |
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 Only | Raid Hours | Wiped 10/22 |, and is it online now?
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | is up at this moment. Counted from its reported uptime, the last restart was about 8 hours ago. 163 of 168 hours up over the last 7 full days, which is 97% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
What does the recorded performance of The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | show?
57 server fps on average over the last 48 hours, and never under 5. Counted at its highest: 127,826 entities, buildings, deployables and the rest of the world included. Memory use peaked at 4,081 MB. A climbing entity count and low fps are the source of what players feel as lag.
In which location is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | hosted?
With its NA tag, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | lists itself in North America. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 104.129.132.49:28129.
What Rust version is recorded for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
On Linux, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.
Counts
What does the population history show for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Current player count on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |: 1, of 20 slots. Averaged across seven days, the player count is 7, with a peak of 29. Averaged over the last 48 hours, the player count is highest at 20:00 UTC: 13 players.
What rank has been recorded for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The same seven-day player-hour count places The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | at #174 within North America, #1,174 across all ranked servers and in the top 5% of them. Ranked #52 among solo servers.
Schedules
On The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, what does the data show for wipe day?
The recent wipes averaged a busiest count of 26 players. 8 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 20% of its recent wipes. In the other cases the crowd was below half by day 4.5.
What wipe schedule has been recorded for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
every Thursday at 18:24 UTC is how The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | wipes. Thursday 29 October at 18:24 UTC is the date its next wipe is due. 5 days ago the current world was made. The tags state a weekly wipe schedule.
Rules and settings
Which settings does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | run, and what rules?
2x gather is stated in the name of The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. Solo play only: teams are not allowed. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.
On which map is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | played?
Custom map at size 4,000 on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, with the file published for download from this page.
Lists and filters
On Rust Graphs, which lists and filters contain The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The Rust Graphs lists that carry The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | are: Servers with a 2x gather rate, Modded Rust servers, Solo Rust servers: group limit 1 and Rust server list: North America. It is returned by these filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Which meaning is attached to each tag on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
gmrust (Game mode): Survival in standard Rust style; mp20 (Max players): The slot count is 20; ts1 (Group limit): The team limit is 1; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^w (Weekly): A wipe occurs every week; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; NA (North America): The server browser lists it under North America; rustmaps (Custom tag): The owner or a plugin set this tag; it is not standard Rust are the tags The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
What is the way to connect to The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Enter client.connect 104.129.132.49:28129 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://discord.com/invite/J8y8ZTjK8y.
Server tags
Published as mp20,ptrak,$r?,v2635,^w,NA,gmrust,cs168909,ts1,rustmaps,^o^z,rustmaps
Game
gmrust
mp20
ts1
v2635
cs168909
ptrak
$r?
Wipe schedule
^w
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.