Working its way up from the back of the class: #14,367 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
51/ 100
D
Moving up: up 215 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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
Top 65% of all ranked servers. 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
No region is published for FULL PVE | 0.5x. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 87.76.55.43:28015 is the address to use.
How dependable is FULL PVE | 0.5x, and is it online at the moment?
At this moment, FULL PVE | 0.5x is offline; the last time it was seen was 17 days 8 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 10 October 2026, Rust Server Score saw it for the first time.
On what Rust version does FULL PVE | 0.5x sit?
Rust network protocol 2634 and build 167398 on Windows is what FULL PVE | 0.5x runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does FULL PVE | 0.5x reset?
FULL PVE | 0.5x has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 17 days 18 hours.
Player numbers
Where does FULL PVE | 0.5x place in the wider field of Rust servers?
In the top 65% of all ranked servers, FULL PVE | 0.5x sits at #14,367 for player hours over the last seven days.
How many players does FULL PVE | 0.5x usually have?
The last sighting of FULL PVE | 0.5x was 17 days 8 hours ago, and it is offline right now.
Tags
What do FULL PVE | 0.5x's tags stand for?
You'll see FULL PVE | 0.5x tagged with gmrust (Game mode): Survival in the standard Rust style; mp64 (Max players): 64 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here 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.
Where does FULL PVE | 0.5x appear in the Rust Server Score lists and filters?
Rust Server Score lists that include FULL PVE | 0.5x: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
Map and rules
How is FULL PVE | 0.5x set up, and what rules does it keep?
FULL PVE | 0.5x sets gather at 0.5x, as its name suggests. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
FULL PVE | 0.5x runs which map?
FULL PVE | 0.5x runs a procedural map, which the game generates.
Getting in
What is the way to join FULL PVE | 0.5x?
To connect, start Rust, press F1, and type client.connect 87.76.55.43:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp64,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp64
Max players64 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
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 momentum (D); standing is the one to work on (F).