This server publishes no banner
Exhibit no. 1,627Acc. 2026.1627
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |
Rust server, NA · in the archive since 13 September 2026
Online NA 216.245.176.156:28025 checked 7m ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
13 Sep Now 17 Sep18:09 1 Oct18:05 · FW 15 Oct18:07 5 Nov19:00 · FW 12 Nov18:07 3 Dec19:00 · FW 10 Dec18:07
a wipe on recordthe monthly force wipeexpectednow, 27 Oct 2026, 14:55 UTCAll times UTC.
The record of each wipe
-
Thu 15 Oct 202618:07 UTC11d ago
- Peak
- 12
- Crowd
- –
- Lasted
- running
- Players before
- 2
-
Thu 1 Oct 202618:05 UTC FW25d ago
- Peak
- 7
- Crowd
- halved by day 7
- Lasted
- 14 days
- Players before
- 0
-
Thu 17 Sep 202618:09 UTC39d ago
- Peak
- 11
- Crowd
- halved by day 1
- Lasted
- 14 days
- Players before
- 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.
The rhythm
Wipe schedule
fixed weekdays
Next wipe Thursday 5 November, 19:00 UTC, in 9d 3h. The force wipe · high confidence
Coming wipes
- 9d 3hThu 5 Nov, 19:00 UTCFW
- 16d 3hThu 12 Nov, 18:07 UTC
- 37d 3hThu 3 Dec, 19:00 UTCFW
- 44d 3hThu 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.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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
Top 7% of all ranked servers, top 13% in NA, and #112 of the duo servers (top 27%). Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags, lists
What do the server tags on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | mean?
The game's server browser reads these tags published by The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: gmrust (Game mode): This server runs standard Rust survival; mp20 (Max players): Slot count: 20; ts2 (Group limit): Teams are capped at 2; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code field is empty; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): Oxide, also known as uMod, is the plugin framework in use; ^z (Modded): Under Modded: the game is changed by plugins or settings; NA (North America): The server browser lists it under North America; rustmaps (Custom tag): The owner or a plugin applied this tag, which is outside the standard Rust set. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.
Which Rust Server History lists and filters include The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
These Rust Server History lists include The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |: 2x Rust servers: the record, Duo Rust servers, Modded Rust servers: the record and North America Rust servers. These filters on the server list bring it up: 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.
The record
Does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run smoothly?
58 server fps on average over the last 48 hours, never below 48. Buildings, deployables and everything else in the world came to as many as 114,155 entities. Memory use peaked at 3,496 MB. What players feel as lag comes from low fps and a climbing entity count.
Which version of Rust does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run?
Rust network protocol 2635 and build 168909 is the build The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | runs, on Windows. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | online, and how reliable is it?
The live count shows The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | online right now. The uptime it reports puts the last restart at about 3 hours ago. It was up for 168 of 168 hours in the last 7 full days, 100% of the time. First seen by Rust Server History on 13 September 2026.
Where is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | located?
In North America, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | lists itself with its NA tag. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. Its entry gives 216.245.176.156:28025 as the address.
Wipe history
What does wipe day look like on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
At their busiest, its recent wipes drew an average of 10 players. At 7 hours after the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. By day 4 it fell below half in the wipes where it did not hold.
What is the wipe schedule on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
A every 4 weeks on Thursday at 18:07 UTC rhythm governs the wipes on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world it runs now dates from 11 days 20 hours ago. The tags list a wipe schedule of every two weeks.
Population
How does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | rank against other Rust servers?
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | ranks #1,627 on seven-day player hours: top 7% overall and #238 in North America. Ranked against other duo servers, it stands at #112.
How busy is The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Against 20 slots, The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | records 0 players right now. The seven-day average stands at 4 players; the peak is 13. The busiest hour of the last 48 was 01:00 UTC, averaging 10 players.
Map and rules
What are the rules and settings on The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
2x gathering is what the name of The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | records. A group may hold 2 players at most (duo). Under game mode, the entry reads survival, gather, build, raid: the standard game. You may fight and raid other players. Under Modded in the server browser, the game is changed by plugins or settings. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.
Which map does The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | run?
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly | runs a custom map of size 4,000; the published file is on this page for download.
Join record
How do I join The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |?
Enter client.connect 216.245.176.156:28025 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you. https://discord.com/invite/J8y8ZTjK8y is its website.
The label explained
Server tags
What each tag this server publishes means.
Published as mp20,ptrak,$r?,v2635,^b,NA,gmrust,cs168909,ts2,^o^z,rustmaps
Game
gmrust
mp20
ts2
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
^z
Region
NA
Other
rustmaps
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.