Online NA 104.129.132.49:28129 checked 9m ago
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |
Connect
srv = rust.server("104.129.132.49:28126")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 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 weekdays
srv.wipe_schedule()Next wipe Thursday 29 October, 18:24 UTC, in 1d 11h. # Every Thursday at 18:24 UTC · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 1d 11h | Thu 29 Oct, 18:24 UTC | wipe |
| 1 | 8d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 15d 11h | Thu 12 Nov, 18:24 UTC | wipe |
| 3 | 22d 11h | Thu 19 Nov, 18:24 UTC | wipe |
| 4 | 29d 11h | Thu 26 Nov, 18:24 UTC | wipe |
| 5 | 36d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 6 | 43d 11h | Thu 10 Dec, 18:24 UTC | wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 18:24 UTC5d ago | 29 | NaN | running | 6 |
| 1 | Thu 15 Oct, 18:02 UTC12d ago | 24 | halved by day 5 | 7 days | 1 |
| 2 | Thu 8 Oct, 18:01 UTC19d ago | 24 | halved by day 5 | 7 days | 5 |
| 3 | Thu 1 Oct, 18:04 UTC FW26d ago | 26 | halved by day 4 | 7 days | 1 |
| 4 | Thu 24 Sep, 18:02 UTC33d ago | 23 | held half | 7 days | 2 |
| 5 | 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.
display(srv.map, srv.info())Map
4000 · seed 1
- map
- Custom Map
- size
- 4000
- seed
- 1
- custom map
- download
Server
srv.info()- address
- 104.129.132.49:28129
- region
- NA
- max players
- 20
- group limit
- solo
- wipe schedule
- weekly
- last wipe
- 22 Oct 2026, 18:24 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | WARBANDITS.GG 2X SOLO ONLY|Loot+|X2 JUST WIPED | NA · solo · 2x · weekly · 47 on average | 80/200 |
| 1 | US Vex.gg 2x Solo Only | 50% Upkeep | JUST WIPED | Max 1 | x2 | NA · solo · 2x · weekly · 5 on average | 1/200 |
| 2 | Bestrust Solo ONLY 2x #5 | JUST FULLWIPED 25.10 10/25 | NA · solo · 2x · weekly · 2 on average | 2/200 |
| 3 | WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED | NA · duo · 2x · weekly · 148 on average | 30/200 |
| 4 | US Limitless 2x Monthly Solo Only|No BP Wipes|Noob Friendly | NA · solo · 2x · monthly · 31 on average | 22/200 |
| 5 | US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just Wiped | NA · duo · 2x · weekly · 8 on average | 10/100 |
Quick answers
From the figures on this page.
Player counts
How does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | compare in the rankings?
Player hours over the last seven days: #1,205 for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, #177 in North America, within the top 5% of the ranked set. The solo group places it at #55.
What population does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | carry?
Current row: 0 players on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, against 20 slots. Over the last seven days it averaged 7 players and peaked at 29. The 48-hour sample puts the busiest hour at 22:00 UTC, averaging 10 players.
Server facts
How smoothly does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | run?
Server fps over the last 48 hours averages 51; the floor is 5. Buildings, deployables and all else in the world took the count as high as 127,403 entities. The memory field tops out at 4,502 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. Joining needs the same protocol on your game; Steam handles the update.
How reliable is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |, and is it up?
Online is the state at the latest refresh for The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. The uptime it reports puts the last restart about 19 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.
In which location is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | hosted?
In North America, The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | lists itself, using the NA tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 104.129.132.49:28129 is its address.
Settings and map
Which settings and rules does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | run?
2x gather is what the name states, and the name is The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |. No teams here: solo only. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | selected?
The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | runs a custom map, size 4,000. The published file is on this page for download.
Wipe schedule
On what schedule does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | wipe?
every Thursday at 18:24 UTC is how The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | wipes. The schedule puts the next wipe on Thursday 29 October at 18:24 UTC. The world it runs now was generated 5 days 12 hours ago. Its tags carry a weekly wipe schedule.
What is wipe day on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | like?
Across recent wipes the busiest point averaged 26 players. The crowd on the latest wipe topped out 8 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 20% of the time. Otherwise the crowd fell below half by day 4.5.
Tags, lists
Where does The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | appear among Rust Data lists and filters?
The Rust Data lists that The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | fits are: Modded Rust servers, 2x Rust servers, Solo Rust servers, group limit 1 and North America Rust servers. Under these filters on the server list, it is listed: 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 meanings do the tags on The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | hold?
These tags are published by The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 | and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): Slot count: 20; ts1 (Group limit): Team size tops out at 1; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^w (Weekly): A wipe every week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; NA (North America): North America is its listing in the server browser; rustmaps (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join The Working Class | 2X | Solo Only | Raid Hours | Wiped 10/22 |?
Enter client.connect 104.129.132.49:28129 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/J8y8ZTjK8y.