StatusLive Servers online11,829 Players89,289 Populated4,008 Wiped · 3 h41 Interval5 min Date28 OCT 2026

DWG RG-S3857Server sheetchecked 2h ago

CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV

Online NA 157.85.92.98:28015 checked 2h ago

2x trio biweekly wipes vanillamoddedcarbon
Connect
Players now 0/ 40 0% full
7-day average1peak 4
Rank#3,857top 17% · #638 in NA
Last wipe12d agobiweekly schedule
Next wipe1d 4hFri 30 Oct, 00:16 UTC
Fig. 1

Players

AveragePeak
00.511.5220:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Fig. 1Players on CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO |...
Fig. 2

Server performance

02040608020:0005:0014:0023:0008:0017:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 17% of all ranked servers, top 34% in NA, and #284 of the trio servers (top 45%). Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 00:16 UTC, in 1d 4h. Its biweekly schedule tag · low confidence

usual gap1 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 4

Coming wipes

  1. 1d 4hFri 30 Oct, 00:16 UTC
  2. 7d 23hThu 5 Nov, 19:00 UTCFW
  3. 15d 4hFri 13 Nov, 00:16 UTC
  4. 29d 4hFri 27 Nov, 00:16 UTC
  5. 35d 23hThu 3 Dec, 19:00 UTCFW
  6. 43d 4hFri 11 Dec, 00:16 UTC

The first 48 hours of its last wipes

Fri 16 OctThu 15 OctWed 14 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 5, 39 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 00:16 UTC12d ago 5 – running 0
Thu 15 Oct, 03:18 UTC13d ago 2 – 0.9 days 0
Wed 14 Oct, 02:52 UTC14d ago 2 – 1 days 0
Tue 13 Oct, 20:01 UTC14d ago 2 – 0.3 days 1
Thu 1 Oct, 20:44 UTC FW26d ago 5 halved by day 4 12 days 1
Thu 17 Sep, 20:11 UTC40d ago 4 held half 14 days 1

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 10 on average
6 / 150
02
WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDNA · trio · 2x · weekly · 187 on average
30 / 200
03
[US] Stevious 2x | Solo/Duo/Trio | 10/22NA · trio · 2x · weekly · 93 on average
3 / 150
04
WARBANDITS.GG 2X Monthly |Solo/Duo/Trio|Shared BPs| Just WipedNA · trio · 2x · monthly · 6 on average
7 / 100
05
The Working Class | 2X | Solo/Duo | Raid Hours | Bi-Weekly |NA · duo · 2x · biweekly · 3 on average
2 / 20
06
Bestrust Solo/Duo/Trio 2x #5 | JUST FULLWIPED 27.10 10/27NA · trio · 2x · weekly · 3 on average
3 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

How reliable is CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV, and is it online now?

At this moment CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV is online. About 6 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 13 September 2026.

What does the recorded performance of CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV show?

The last 48 hours give an average of 59 server fps and a floor of 26. Counted at its highest: 40,444 entities, buildings, deployables and the rest of the world included. 3,966 MB is the memory peak. Players feel low fps and a climbing entity count as lag.

In which location is CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV hosted?

In North America CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV lists itself, tagged NA. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 157.85.92.98:28015.

What Rust version is recorded for CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV?

On Linux, CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.

Counts

How many players are plotted on CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV?

0 of 40 slots on CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV are taken at the latest refresh. The seven-day mean is 1 players; the peak over the same period is 4. Over the last 48 hours the busiest hour was 07:00 UTC, at an average of 2 players.

Against other Rust servers, where is CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV placed?

Across seven days, player hours give CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV #3,857 globally and #638 in North America, a top 17% position among ranked servers. #284 against other trio servers.

Wipe data

What is recorded on CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV on wipe day?

At their busiest, its recent wipes drew 3 players on average. 39 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 50% of its recent wipes stayed above half that peak. By day 4 the crowd had fallen below half on the wipes where it did not hold.

What wipe schedule has been recorded for CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV?

The prediction follows its tag, because too few wipes of CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV are on record to confirm the schedule. It is due to wipe next on Friday 30 October at 00:16 UTC. The current world has been in use since 12 days 19 hours ago. Its tags give a wipe schedule of one wipe every two weeks.

Settings

What settings and rules apply on CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV?

CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV takes its gather rate from its name: 2x. Groups: 3 players maximum (trio). It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Carbon. It describes itself as vanilla, by which it means rates, kits and rules are unchanged from Facepunch's release. VAC is on: that is Valve's anti-cheat.

On which map is CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV played?

Size 2,500 with seed 32323: that is the procedural map CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

On Rust Graphs, which lists and filters contain CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV?

On Rust Graphs, CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV is placed in these lists: Servers with a 2x gather rate, Modded Rust servers, Trio Rust servers, plotted live and Rust server list: North America. These filters on the server list return it: Region: North America; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.

On CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): Slots: 40; ts3 (Group limit): Team size is capped at 3; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^z (Modded): Plugins or settings change the game, so it is listed under Modded; ^y (Carbon): The plugin framework is Carbon; NA (North America): The browser's listing places it under North America are the tags CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

What is the way to connect to CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIV?

Connect with client.connect 157.85.92.98:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://discord.com/invite/MFsD5u6dG5.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,^z,^y,^b,^v,NA,gmrust,cs168909,ts3

Game

gmrust
Game mode Standard survival, as Rust plays.
mp40
Max players Slots: 40.
ts3
Group limit Team size is capped at 3.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Mods and access

^z
Modded Plugins or settings change the game, so it is listed under Modded.
^y
Carbon The plugin framework is Carbon.

Region

NA
North America The browser's listing places it 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.

KeyTag string decoded