[BR] SOLO/DUO Bi-weekly Softcore
Offline 157.85.89.93:20130 checked 3d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 69% of all ranked servers, and #627 of the quad servers (top 76%). Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 21:43 UTC4d ago | 0 | – | running | 0 |
| Tue 22 Sep, 10:15 UTC35d ago | 1 | halved by day 1 | 31.5 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| EL MATADERO | SA · quad · biweekly · 2 on average | 0 / 50 |
| PACIFIC RUST | Vanilla + Modo Pacífico|Max Squad|Wipe Mensal | SA · quad · monthly · 1 on average | 1 / 200 |
| [LATAM] VAINILLA Solo/Duo/Trio/Quad | 26/10 Full Wipe | SA · quad · weekly · 9 on average | 5 / 200 |
| [BR/LATAM] LEGEND CLT | SOLO-QUAD | WIPED 23/10 [UR,PY,AR] | SA · quad · biweekly · 9 on average | 10 / 120 |
| [BR] GURIZADA BR [Quinzenal] [SOLO/DUO] | SA · quad · biweekly · 5 on average | 3 / 100 |
| SKOL LATAO BR [CLT] - QUAD - WIPE 22/10 | SA · quad · weekly · 3 on average | 2 / 100 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for [BR] SOLO/DUO Bi-weekly Softcore: what is it?
With too few of its wipes on record, [BR] SOLO/DUO Bi-weekly Softcore's rhythm is not yet clear. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world now in play was created 4 days 1 hours ago.
Wipe day on [BR] SOLO/DUO Bi-weekly Softcore: what should you expect?
Recent wipes averaged a busiest count of 0 players. Peak population for the latest wipe came 0 hours after it began. Above half that peak until the next wipe held in 0% of recent wipes. The fall below half arrived by day 1 when it didn't hold.
Server details
What is the hosting location of [BR] SOLO/DUO Bi-weekly Softcore?
The name of [BR] SOLO/DUO Bi-weekly Softcore points to South America, though no region tag is published. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 157.85.89.93:20130 is its address.
What Rust build does [BR] SOLO/DUO Bi-weekly Softcore run?
On Linux, [BR] SOLO/DUO Bi-weekly Softcore runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.
What uptime does [BR] SOLO/DUO Bi-weekly Softcore show, and is it up?
Offline at this refresh: [BR] SOLO/DUO Bi-weekly Softcore, last seen 3 days 19 hours ago. 4% uptime over the last 7 full days, equal to 7 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.
Tags
How should the tags on [BR] SOLO/DUO Bi-weekly Softcore be read?
The game's server browser reads the tags [BR] SOLO/DUO Bi-weekly Softcore publishes: gmsoftcore (Game mode): Softcore ruleset, the easier one; mp30 (Max players): Capacity of 30 slots; ts4 (Group limit): Team size is capped at 4; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Modded listing, where plugins or settings change the game. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
On Rust Server Analytics, which lists and filters feature [BR] SOLO/DUO Bi-weekly Softcore?
Among the Rust Server Analytics lists [BR] SOLO/DUO Bi-weekly Softcore fits are: Modded Rust servers: live data. It appears on the server list under the following filters: Region: South America; Type: Modded; Game mode: Softcore; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Last wipe: In the last week.
Population
Against other Rust servers, how does [BR] SOLO/DUO Bi-weekly Softcore compare?
On player hours over seven days, [BR] SOLO/DUO Bi-weekly Softcore ranks #15,405, within the top 69% of ranked servers. The quad segment places it at #627.
At what level does [BR] SOLO/DUO Bi-weekly Softcore run its population?
[BR] SOLO/DUO Bi-weekly Softcore is offline at this refresh; the last contact was 3 days 19 hours ago. The seven-day mean for this server is 0 players.
Settings
What settings and rules does [BR] SOLO/DUO Bi-weekly Softcore use?
Gather rate is not mentioned in the name of [BR] SOLO/DUO Bi-weekly Softcore. Groups: quad, capped at 4 players. softcore is the game mode, Part of your loot stays with you in this easier Facepunch mode. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. VAC, Valve's anti-cheat, is enabled.
The map on [BR] SOLO/DUO Bi-weekly Softcore: which one is it?
The game generates a procedural map of size 3,500 with seed 16765234 for [BR] SOLO/DUO Bi-weekly Softcore. Size and seed fix the map, so a RustMaps view is available from this page.
Connection
How can a player join [BR] SOLO/DUO Bi-weekly Softcore?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 157.85.89.93:20130.