Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region tag appears for [BR] RICA_RUST_PVE, but the name suggests South America. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 200.192.101.206:28016.
How reliable is [BR] RICA_RUST_PVE, and is it up?
At this moment, [BR] RICA_RUST_PVE is offline; the last time it was seen was 40 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 19 September 2026.
Which Rust version is [BR] RICA_RUST_PVE running?
You will find [BR] RICA_RUST_PVE on Rust network protocol 2633 and build 164530, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does [BR] RICA_RUST_PVE wipe its map?
There are too few wipes on record for [BR] RICA_RUST_PVE to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 40 days 22 hours.
Player count
Where does [BR] RICA_RUST_PVE sit among Rust servers?
In the top – of all ranked servers, [BR] RICA_RUST_PVE sits at #14,909 for player hours over the last seven days.
Is [BR] RICA_RUST_PVE a busy server?
The last sighting of [BR] RICA_RUST_PVE was 40 days 19 hours ago, and it is offline right now.
Tags
What do [BR] RICA_RUST_PVE's tags stand for?
You'll see [BR] RICA_RUST_PVE tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp30 (Max players): Its slot count is 30; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature [BR] RICA_RUST_PVE?
These Rust Server Score lists count [BR] RICA_RUST_PVE among them: Modded Rust servers, graded. These filters bring it up on the server list: Region: South America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does [BR] RICA_RUST_PVE enforce, and what are its settings?
The name of [BR] RICA_RUST_PVE gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [BR] RICA_RUST_PVE uses?
A procedural map, generated by the game, is what [BR] RICA_RUST_PVE runs.
How to join
What is the way to join [BR] RICA_RUST_PVE?
To connect, start Rust, press F1, and type client.connect 200.192.101.206:28016. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp30
Max playersIts slot count is 30.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.
Not enough figures yet to write a report. Check back after a few days on the list.