RustyBrawls | CAN | Solo/Duo
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 10m ago · 209.89.169.161:28060
Abstract
We describe the public Rust server RustyBrawls | CAN | Solo/Duo, reached at 209.89.169.161:28060 and hosted in NA. At the last check it held 0 of 100 places, against a seven-day mean of 0 and a peak of 21. It ranks #4,263 of all servers, the top 19%, and #718 in NA. It last wiped 26d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsduo monthly wipes vanilla oxide premium
1Summary statistics

2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 19% of all ranked servers, the top 38% in NA, and #235 of the duo servers (top 56%). Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: force wipes only
The next wipe is expected Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 4 | players, last three wipes |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 8d 15h | force wipefw |
| Thu 3 Dec, 19:00 | 36d 15h | force wipefw |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 1 Oct, 18:30fw26d ago | 4 | – | running | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 209.89.169.161:28060 |
|---|---|
| Region | NA |
| Max players | 100 |
| Group limit | duo |
| Wipe schedule | monthly |
| Last wipe | 1 Oct 2026, 18:30 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3200 |
| Seed | 1 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are North American Rust servers [2], servers with a group limit of 2 [3], rust community servers listed [4], 1x rust servers [5] and upcoming Rust wipes [6].
| Server | Players |
|---|---|
| k1 solo duoNA · duo · monthly · 1 on average | 3/50 |
| RustedAK NOOBS DUO SOLOsNA · duo · monthly · 1 on average | 1/250 |
| Edmonton Softcore RustNA · duo · monthly · 3 on average | 6/50 |
| RustForNoobs.com | Solo/Duo | Weekly | USNA · duo · weekly · 100 on average | 33/100 |
| RustForNoobs.com | Mondays | Solo/Duo | USNA · duo · weekly · 60 on average | 246/275 |
| Lone Wolf Rust | Solo Only, Monthly, Vanilla, No BP WipesNA · solo · monthly · 36 on average | 39/100 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1How well does RustyBrawls | CAN | Solo/Duo run?
Over the past 48 hours, it ran at an average of 116 server fps, with a low of 109. Buildings, deployables and all other world objects counted together reached a maximum of 58,389 entities. Memory use peaked at 2,288 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.
A.2What is the location of RustyBrawls | CAN | Solo/Duo?
In North America, according to its own listing, RustyBrawls | CAN | Solo/Duo appears with the NA tag. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 209.89.169.161:28060.
A.3What is the online status and reliability of RustyBrawls | CAN | Solo/Duo?
RustyBrawls | CAN | Solo/Duo is currently online. The uptime it reports indicates a restart about 16 hours ago. The server was up 100% of the time over the last 7 full days, 168 of 168 hours. Its first appearance in Rust Statistics's records is 13 September 2026.
A.4What version of Rust is run on RustyBrawls | CAN | Solo/Duo?
The version of Rust on RustyBrawls | CAN | Solo/Duo is network protocol 2635 and build 168909, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.5What schedule does RustyBrawls | CAN | Solo/Duo follow for wipes?
Once a month, RustyBrawls | CAN | Solo/Duo wipes in line with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. The current world has been running for 26 days 8 hours. A monthly wipe schedule is stated in the server's tags.
A.6What happens on RustyBrawls | CAN | Solo/Duo when wipe day arrives?
The average busiest point of recent wipes was 4 players. The peak on the latest wipe came 29 hours after it began.
Player count
A.7How does RustyBrawls | CAN | Solo/Duo compare with other Rust servers in the rankings?
The seven-day player-hours ranking gives RustyBrawls | CAN | Solo/Duo #4,263, in the top 19% of ranked servers and #718 in North America. It ranks #235 among servers in the duo group.
A.8How would you characterise the player activity on RustyBrawls | CAN | Solo/Duo?
The current population of RustyBrawls | CAN | Solo/Duo is 0, drawn from 100 slots. The peak over seven days is 2, against an average of 0. Averaging 2 players, 00:00 UTC was the busiest hour of the past 48.
Tags and filters
A.9How should the tags on RustyBrawls | CAN | Solo/Duo be interpreted?
The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): 100 slots are available; ts2 (Group limit): Teams are capped at 2; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^m (Monthly): A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe; ^v (Vanilla): This is the game as Facepunch ships it, with rates, kits and rules unaltered; ^q (Premium): Rust's premium status is required to join; ^o (Oxide): The plugin framework in use is Oxide (uMod); NA (North America): The server browser lists this server under North America, which RustyBrawls | CAN | Solo/Duo publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.10Where can RustyBrawls | CAN | Solo/Duo be found among the Rust Statistics lists and filters?
Duo Rust servers, group limit 2, Rust community servers, measured, North American server statistics and Vanilla Rust servers are the Rust Statistics lists that RustyBrawls | CAN | Solo/Duo fits. These filters on the server list return it: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Monthly ^m, Vanilla ^v, Premium ^q and Oxide ^o; Group limit: Duo; Wipe schedule: Monthly.
Settings and map
A.11Which settings and rules are in force on RustyBrawls | CAN | Solo/Duo?
Its name carries no gather rate for RustyBrawls | CAN | Solo/Duo. duo sets the team size at 2 players. Listed as survival, the game mode is gather, build and raid: the standard game. Players may raid and fight one another. It is a community server, as the browser's Community listing shows. Plugins number Oxide on this server. The server's own description is vanilla: this is the game as Facepunch ships it, with rates, kits and rules unaltered. Rust's premium status is required to join. VAC, Valve's anti-cheat, is enabled.
A.12What map is in use on RustyBrawls | CAN | Solo/Duo?
The game generates RustyBrawls | CAN | Solo/Duo's procedural map at size 3,200, from seed 1. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
Connection
A.13What is the process for joining RustyBrawls | CAN | Solo/Duo?
Enter client.connect 209.89.169.161:28060 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. Rust's premium status is required to join. The website for this server is https://discord.com/invite/HWYQtdtGPd.
Appendix BServer tags
What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,^m,^v,NA,gmrust,cs168909,^q,ts2,^o.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp100 | Max players. 100 slots are available. |
ts2 | Group limit. Teams are capped at 2. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. The region code is unset. |
| Wipe schedule | |
^m | Monthly. A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe. |
| Difficulty | |
^v | Vanilla. This is the game as Facepunch ships it, with rates, kits and rules unaltered. |
| Mods and access | |
^q | Premium. Rust's premium status is required to join. |
^o | Oxide. The plugin framework in use is Oxide (uMod). |
| Region | |
NA | North America. The server browser lists this server under North America. |
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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. North American Rust servers. ruststatistics.org/top-us-rust-servers.
- [3]Rust Statistics. Servers with a group limit of 2. ruststatistics.org/top-duo-rust-servers.
- [4]Rust Statistics. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
- [5]Rust Statistics. 1x rust servers. ruststatistics.org/top-vanilla-rust-servers.
- [6]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.