Working its way up from the back of the class: #15,986 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
33/ 100
F
Lost ground: down 5,459 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
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
Top 71% 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 peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 02:15 UTC24d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by FAZE UP!. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 183.197.173.148:28017.
Is FAZE UP! up, and how steady is its uptime?
At this moment, FAZE UP! is offline; the last time it was seen was 24 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 4 October 2026, Rust Server Score saw it for the first time.
What Rust version is FAZE UP! on?
You will find FAZE UP! on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does FAZE UP! wipe, and how often?
FAZE UP! has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 24 days 14 hours have passed since this world was made.
What happens on FAZE UP! when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 1 hours into the latest wipe.
Population
Where does FAZE UP! sit among Rust servers?
Over the last seven days, FAZE UP! has #15,986 for player hours, in the top 71% of all ranked servers.
What does the population on FAZE UP! look like?
FAZE UP! is offline at the moment; the last time it was seen was 24 days 12 hours ago.
Tags
How should you read the tags on FAZE UP!?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^p (PvE): The danger comes from the world, not from other players; ^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 FAZE UP! 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.
Which Rust Server Score filters and lists feature FAZE UP!?
These Rust Server Score lists count FAZE UP! among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does FAZE UP! enforce, and what are its settings?
Nothing in the name of FAZE UP! states a gather rate. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
FAZE UP! runs which map?
The game generates a procedural map for FAZE UP!.
Connecting
What is the way to join FAZE UP!?
To connect, start Rust, press F1, and type client.connect 183.197.173.148:28017. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,^p,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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. Even marks across the subjects, from F to F.