Station NA-1807 · recording
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |
Online NA 216.245.176.156:28025 checked 12m ago
- Players now
- 1/ 20
- 5% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 3
- peak 11
- Rank
- #1,807
- top 8% · #278 in NA
- Last wipe
- 13d ago
- biweekly schedule
- Next wipe
- 7d 2h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 20 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- −2into Thu 02:00 UTC
- Peak · 48 h
- 7most players in any hour
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
daily · 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 weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
- usual gap
- 28 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 10players, last three wipes
- crowd held
- 0%else halves by day 4
Coming wipes
- 7d 2hThu 5 Nov, 19:00 UTCFW
- 14d 1hThu 12 Nov, 18:07 UTC
- 35d 2hThu 3 Dec, 19:00 UTCFW
- 42d 1hThu 10 Dec, 18:07 UTC
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 18:07 UTC13d ago | M1.0▲rising | 12 | – | running | 2 | |
| Thu 1 Oct, 18:05 UTC FW27d ago | M0.8▲rising | 7 | halved by day 7 | 14 days | 0 | |
| Thu 17 Sep, 18:09 UTC41d ago | M1.0▲rising | 11 | halved by day 1 | 14 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
At size 4,000, the map on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is custom and its published file can be downloaded from this page.
Which settings and rules apply on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Its name points to a gather rate of 2x on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. You can have up to 2 players in a group (duo). It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | right now?
At this moment, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | records 1 players across 20 slots. Across seven days this server recorded an average of 3 players and a peak of 11. Averaged over the last 48 hours, the busiest hour was 01:00 UTC at 6 players.
How does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | rank against other Rust servers?
For player hours across the last seven days, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | takes #1,807 overall and #278 in North America, inside the top 8% of all ranked servers. It sits at #122 among duo servers.
Server details
How reliably does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | stay online?
Right now, you can reach The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. Going by the uptime figure it reports, it restarted about 3 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | hold a steady tick rate?
Its average server fps over the last 48 hours was 58, and it never dropped below 48. The world held up to 113,832 entities at its peak, buildings and deployables included. Its highest memory use was 3,565 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run from?
With its NA tag, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lists itself in North America. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 216.245.176.156:28025.
Which Rust version is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | running?
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
10 players, on average, was the busiest crowd at its recent wipes. 7 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 4.
How often does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | wipe, and on which days?
At The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | the wipes follow a every 4 weeks on Thursday at 18:07 UTC rhythm. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 13 days 22 hours. Every two weeks it wipes, according to the schedule in its tags.
Server tags
What do the server tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | mean?
Tags published by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp20 (Max players): 20 slots are available; ts2 (Group limit): Each team can hold up to 2; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; NA (North America): North America is the region it's listed under in the browser; rustmaps (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | appear?
You will find The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | on the following Rust Server Trends lists: 2x Rust servers, listed live, Duo Rust servers, group limit 2, Modded Rust servers, tracked live and North America Rust servers. You will find it under these filters on the server list: 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.
Connecting
What steps get you onto The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
To join, enter client.connect 216.245.176.156:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. https://discord.com/invite/J8y8ZTjK8y is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.