Online NA 216.245.176.156:28025 checked 8m ago
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |
Connect
srv = rust.server("216.245.176.156:28027")
print(srv.connect_command)Right now
srv.summary()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 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 · fixed weekdays
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 14d 6h | Thu 12 Nov, 18:07 UTC | wipe |
| 2 | 35d 7h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 42d 6h | Thu 10 Dec, 18:07 UTC | wipe |
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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 18:07 UTC13d ago | 12 | NaN | running | 2 |
| 1 | Thu 1 Oct, 18:05 UTC FW27d ago | 7 | halved by day 7 | 14 days | 0 |
| 2 | 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.
display(srv.map, srv.info())Map
4000 · seed 1337
- map
- Custom Map
- size
- 4000
- seed
- 1337
- custom map
- download
Server
srv.info()- address
- 216.245.176.156:28025
- region
- NA
- max players
- 100
- group limit
- duo
- wipe schedule
- biweekly
- last wipe
- 15 Oct 2026, 18:07 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/Duo|X2 JUST FULLWIPED | NA · duo · 2x · weekly · 143 on average | 98/200 |
| 1 | US Limitless 2x Monthly Solo/Duo|No BP Wipes|Noob Friendly | NA · duo · 2x · monthly · 56 on average | 29/200 |
| 2 | US RENEGADE 2x Monthly | Solo Duo | 50% Upkeep | No BP Wipe | NA · duo · 2x · monthly · 25 on average | 8/150 |
| 3 | HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED | NA · trio · 2x · biweekly · 10 on average | 5/150 |
| 4 | US Limitless 2x Solo/Duo | No BP Wipes|Noob Friendly|Just Wiped | NA · duo · 2x · weekly · 8 on average | 4/100 |
| 5 | US Rusty Rats 2x Monthly | Solo/Duo | 50% Upkeep | No BP Wipe | NA · duo · 2x · monthly · 5 on average | 2/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | rank?
Ranked #1,795 on seven-day player hours, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is #276 in North America and in the top 8% of all ranked servers. Its position in the duo group is #122.
What population does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | carry?
The sample now reads 0 players for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, out of 100 slots. Over the last seven days it averaged 3 players and peaked at 11. Averaged by hour over 48 hours, 01:00 UTC is the busiest, at 6 players.
About the server
How well does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | perform?
The 48-hour average is 57 server fps, with a low of 46. Entity numbers reached 113,832, and that includes buildings, deployables and the rest. The memory field tops out at 3,565 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. Joining needs the same protocol on your game; Steam handles the update.
How reliable is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |, and is it online now?
Online is the state at the latest refresh for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. A restart about 22 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | sit?
With its NA tag, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lists itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 216.245.176.156:28025 is its address.
Map and rules
Which settings and rules does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run?
2x gather is what the name states, and the name is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. Up to 2 players may share a group (duo). Recorded as survival, 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. VAC is running: Valve's anti-cheat is on.
Which map has The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | selected?
Map size 4,000, custom, on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. Download the published file from this page.
Wipe schedule
When does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe, and how often?
The wipe rhythm for The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is every 4 weeks on Thursday at 18:07 UTC. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 13 days 17 hours ago. The tags list a two-weekly wipe cycle.
What is wipe day on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | like?
The average peak over recent wipes is 10 players. Peak population on the latest wipe came 7 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 4 in the other cases.
Lists and tags
Where does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear among Rust Data lists and filters?
These Rust Data lists include The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: Rust servers with a duo group limit, Modded Rust servers, 2x Rust servers and North America Rust servers. Under these filters on the server list, it is listed: 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.
How should you read the server tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
These tags are published by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts2 (Group limit): No team may exceed 2; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^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): The server browser files it under North America; rustmaps (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
In Rust, F1 opens the console: type client.connect 216.245.176.156:28025. Launch Rust on this page does the same by opening the game through Steam and connecting. https://discord.com/invite/J8y8ZTjK8y is the website recorded for it.