Working its way up from the back of the class: #14,414 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
22/ 100
F
Lost ground: down 7,946 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.
AveragePeak
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 13 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers, and #596 of the quad servers (top 73%). Ranked on player hours over the last seven days.
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
Where in the world is FaZa Rust | Vanilla+ | TEST?
You'll find no region listed by FaZa Rust | Vanilla+ | TEST. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 178.187.44.106:28015 is the address to use.
How reliable is FaZa Rust | Vanilla+ | TEST, and is it up?
You cannot join now: FaZa Rust | Vanilla+ | TEST is offline, last seen 11 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 October 2026.
Which Rust version is FaZa Rust | Vanilla+ | TEST running?
You will find FaZa Rust | Vanilla+ | TEST on Rust network protocol 2634 and build 166586, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does FaZa Rust | Vanilla+ | TEST reset?
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. The world it runs now was created 17 days 1 hours.
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,414 for player hours, in the top 67% of all ranked servers. It comes #596 among servers in the quad group.
How many players does FaZa Rust | Vanilla+ | TEST usually have?
The last sighting of FaZa Rust | Vanilla+ | TEST was 11 days 23 hours ago, and it is offline right now.
Tags
What is meant by the tags on FaZa Rust | Vanilla+ | TEST?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): Its slot count is 5; ts4 (Group limit): A team can hold 4 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $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. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does FaZa Rust | Vanilla+ | TEST appear in the Rust Server Score lists and filters?
Rust Server Score lists that include FaZa Rust | Vanilla+ | TEST: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad.
Map and rules
What settings and rules apply on FaZa Rust | Vanilla+ | TEST?
You will find no gather rate in the name of FaZa Rust | Vanilla+ | TEST. You can have up to 4 players in a group (quad). You get survival here, gather and build and raid: 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 FaZa Rust | Vanilla+ | TEST uses?
The game generates the procedural map on FaZa Rust | Vanilla+ | TEST at size 3,000 with seed 123456. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto FaZa Rust | Vanilla+ | TEST?
Enter client.connect 178.187.44.106: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?,v2634,gmrust,cs166586,ts4,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max playersIts slot count is 5.
ts4
Group limitA team can hold 4 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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).