The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |
Offline NA 104.129.132.49:28129 checked 15h ago
Server instruments
last reading Wed 09:00 UTCPlayers now
0% full 7-day avg7-day peak 29, past the slotsServer fps
48 h low 5 · below 20 is lag, below 10 is badEntities
48 h range 101,504–127,227 · memory 4,356 MBUptime
23 h 3 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 5% of all ranked servers, top 9% in NA, and #55 of the solo servers (top 25%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 29 October, 18:24 UTC, in 16h. Every Thursday at 18:24 UTC · high confidence
Coming wipes
- WPT 1Thu 29 Oct, 18:24 UTC16h
- WPT 2Thu 5 Nov, 19:00 UTC7d 17hFW
- WPT 3Thu 12 Nov, 18:24 UTC14d 16h
- WPT 4Thu 19 Nov, 18:24 UTC21d 16h
- WPT 5Thu 26 Nov, 18:24 UTC28d 16h
- WPT 6Thu 3 Dec, 19:00 UTC35d 17hFW
- WPT 7Thu 10 Dec, 18:24 UTC42d 16h
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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 18:24 UTC6d ago | 29 | – | running | 6 |
| Thu 15 Oct, 18:02 UTC13d ago | 24 | halved by day 5 | 7 days | 1 |
| Thu 8 Oct, 18:01 UTC20d ago | 24 | halved by day 5 | 7 days | 5 |
| Thu 1 Oct, 18:04 UTC FW27d ago | 26 | halved by day 4 | 7 days | 1 |
| Thu 24 Sep, 18:02 UTC34d ago | 23 | held half | 7 days | 2 |
| Thu 17 Sep, 18:07 UTC41d 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
the same kind of game, then region, group limit, rate and wipes- 46/200
- 3/200
- 2/200
- 438/550
- 35/200
- 15/100
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
The busiest point of its recent wipes drew 26 players on average. 8 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 20% of its recent wipes. When it didn't hold, by day 4.5 it fell below half.
When does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | wipe?
Wipes on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | come every Thursday at 18:24 UTC. On Thursday 29 October at 18:24 UTC its next wipe is due. The world it runs now was made 6 days 7 hours ago. Its tags carry a weekly wipe schedule.
Tags
How should you read the tags on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): The server holds 20 slots; ts1 (Group limit): Teams are capped at 1; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): North America is the browser category it sits in; rustmaps (Custom tag): A plugin or the owner set this tag; Rust does not ship it from The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Rust Metrics lists featuring The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |: 2x Rust servers, checked live, Modded Rust servers, checked live, Solo-only Rust servers and North America: server readout. Reading: server list filters. It comes up under 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.
Player count
What position does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | hold among Rust servers?
Ranked by seven-day player hours, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | sits at #1,208 and #176 in North America, inside the top 5%. The solo group places it at #55.
What player count does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | carry?
Reading for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |: offline at this moment; last seen 15 hours ago. Check: players over seven days. Average 7, peak 29. The last 48 hours peaked at 02:00 UTC, averaging 6 players at that hour.
Operator and location
What location is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | hosted in?
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | gives North America as its location, with the NA tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 104.129.132.49:28129.
What Rust version is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. To get in, your game needs the same protocol; Steam applies the update.
How does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | perform?
Over the last 48 hours the average was 43 server fps; the floor was 5. Check: entities. The peak was 127,227, counting buildings, deployables and the rest of the world. Memory peak: 4,502 MB. Expect lag when fps falls and entities climb.
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 | reports offline. The last reading came 15 hours ago. Check: restart. The uptime it reports puts the last restart about 23 hours ago. Reading: 92% uptime over the last 7 full days. It was up 154 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
How is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | configured, and what rules are in force?
The name carries the rate: 2x gather on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. Check: teams. Solo only — no teams. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Which map is live on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Check: map. A custom one of size 4,000, run by The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. The published file can be downloaded from this page.
Connection
How do you connect to The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Check: join. Open Rust, press F1, then enter client.connect 104.129.132.49:28129. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/J8y8ZTjK8y is where its website sits.