Server profile · NA
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |
Online, with 0 of 20 players on; ranked #1,200 of every public Rust server, the top 5%. It last wiped 5d ago.
Online NA 104.129.132.49:28129 checked 9m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 5% of all ranked servers, top 9% in NA, and #54 of the solo servers (top 25%). Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Fixed weekdays.
Next wipe Thursday 29 October, 18:24 UTC, in 1d 14h. Every Thursday at 18:24 UTC · high confidence
Coming wipes
- 1d 14hThu 29 Oct, 18:24 UTC
- 8d 14hThu 5 Nov, 19:00 UTCFW
- 15d 14hThu 12 Nov, 18:24 UTC
- 22d 14hThu 19 Nov, 18:24 UTC
- 29d 14hThu 26 Nov, 18:24 UTC
- 36d 14hThu 3 Dec, 19:00 UTCFW
- 43d 14hThu 10 Dec, 18:24 UTC
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 29, 8 hours in.
The record
Wipes
Every wipe we saw, newest first.
| 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 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- WARBANDITS.GG 2X SOLO ONLY|Loot+|X2 JUST WIPED118/200
- US Vex.gg 2x Solo Only | 50% Upkeep | JUST WIPED | Max 1 | x21/200
- Bestrust Solo ONLY 2x #5 | JUST FULLWIPED 25.10 10/252/200
- WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED35/200
- US Limitless 2x Monthly Solo Only|No BP Wipes|Noob Friendly22/200
- US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just Wiped21/100
The short version
Quick answers
From the figures on this page.
Wipe days
What does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | look like once wipe day arrives?
The average busiest point of its recent wipes was 26 players. 8 hours after the latest wipe, the crowd peaked. In 20% of recent wipes, more than half the peak was still playing at the next wipe. The cases that did not hold saw the crowd fall below half by day 4.5.
On what schedule does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | wipe?
On The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, wipes are scheduled every Thursday at 18:24 UTC. Thursday 29 October at 18:24 UTC is when the next wipe is due. This world dates from 5 days 9 hours ago. The tags list wipes as weekly.
About the server
How well does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | perform?
The 48-hour average for server fps is 52, and 5 was the lowest seen. At its highest the entity count reached 127,722: buildings, deployables and everything else. The highest memory figure was 4,502 MB. What players feel as lag comes from low fps and an entity count on the rise.
On what version does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | currently run?
Rust network protocol 2635 and build 168909 on Linux is what The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | runs. The same protocol is required to join, and Steam takes care of updating it.
What does uptime look like for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, and is it online?
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | is currently reachable and online. Going by the uptime figure it gives, its last restart was around 17 hours ago. The last 7 full days gave 167 of 168 hours up, or 99% of the time. The first record Rust Insights has of it is 13 September 2026.
In which location does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | sit?
Its NA tag is what The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | uses to list itself in North America. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. Connect through 104.129.132.49:28129.
Lists and tags
What is meant by each tag on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
When the game's server browser reads The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): 20 slots in total; ts1 (Group limit): A team holds 1 players at most; v2635 (Protocol): Your game must run the same version to join: the protocol is 2635; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): No region code is set; ^w (Weekly): The cycle repeats each week; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; NA (North America): Its browser listing sits under North America; rustmaps (Custom tag): A plugin or the owner set this tag; it is not one of Rust's standard tags. Current players, queue length and the age of the world sit in the tags as well, shown at the top of this page.
Which Rust Insights filters and lists feature The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | appears among the following Rust Insights lists: Rust servers with a 2x gather rate, Modded Rust servers, explained, Solo Rust servers and North American Rust servers. You will find it on the server list by applying these filters: 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.
Population history
What does the population of The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | look like?
At the time of this refresh, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | holds 0 players on 20 slots. A weekly average of 7 players goes with a peak of 29. The busiest point of the last 48 hours fell at 22:00 UTC, averaging 10 players.
In the ranking of Rust servers, where does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | place?
On the seven-day player-hours measure, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | is #1,200, in the top 5% of all ranked servers and #176 in North America. Within its solo group, the position is #54.
Settings and rules
What are the settings and rules for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Going by its name, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | gathers at 2x. This is a solo-only server, with no teams. You get survival as the game mode, the standard game: gather, build, raid. Players may raid and fight one another. Plugins or settings change the game, so it sits under Modded in the browser. Plugins: Oxide run here. VAC is on: Valve's anti-cheat is active.
What is the map on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The map on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | is custom, size 4,000, with its file published for download here.
How to join
How can you get onto The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
To connect, start Rust and enter client.connect 104.129.132.49:28129 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you. Its website can be found at https://discord.com/invite/J8y8ZTjK8y.