Working its way up from the back of the class: #14,254 on player hours.
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
21/ 100
F
Lost ground: down 8,290 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum is the one to work on (F).
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.
AveragePeakWipe
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 32 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 23 Sep, 08:54 UTC36d ago
3
–
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. 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
Where in the world is FaZa Rust | Vanilla+ | TEST?
No region is published for FaZa Rust | Vanilla+ | TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 178.186.72.190:28015 is the address to use.
How dependable is FaZa Rust | Vanilla+ | TEST, and is it online at the moment?
The server is down: FaZa Rust | Vanilla+ | TEST is offline now, with the last sighting 28 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 23 September 2026, Rust Server Score saw it for the first time.
What Rust version is FaZa Rust | Vanilla+ | TEST on?
You will find FaZa Rust | Vanilla+ | TEST on Rust network protocol 2633 and build 165217, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does FaZa Rust | Vanilla+ | TEST wipe, and how often?
The record holds too few of FaZa Rust | Vanilla+ | TEST's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 35 days 22 hours have passed since this world was made.
What happens on FaZa Rust | Vanilla+ | TEST when wipe day arrives?
The average peak on its recent wipes was 3 players. 32 hours after the latest wipe began, the crowd hit its peak.
Population
Where does FaZa Rust | Vanilla+ | TEST place in the wider field of Rust servers?
Over the last seven days, FaZa Rust | Vanilla+ | TEST has #14,254 for player hours, in the top 60% of all ranked servers.
What does the population on FaZa Rust | Vanilla+ | TEST look like?
It has been 28 days 2 hours since FaZa Rust | Vanilla+ | TEST was last seen, and it is offline right now.
Tags and filters
How should you read the tags on FaZa Rust | Vanilla+ | TEST?
gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): 5 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags FaZa Rust | Vanilla+ | TEST publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature FaZa Rust | Vanilla+ | TEST?
Rust Server Score lists that include FaZa Rust | Vanilla+ | TEST: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is FaZa Rust | Vanilla+ | TEST set up, and what rules does it keep?
Nothing in the name of FaZa Rust | Vanilla+ | TEST states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. 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.
Which map is in play on FaZa Rust | Vanilla+ | TEST?
A procedural map of size 3,000 and seed 123456, generated by the game, is what FaZa Rust | Vanilla+ | TEST runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join FaZa Rust | Vanilla+ | TEST?
Enter client.connect 178.186.72.190:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp5
Max players5 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).