Working its way up from the back of the class: #14,419 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
53/ 100
D
Moving up: up 800 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 67% 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
FULL PVE | 0.5x leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 45.153.50.47:28015.
How reliable is FULL PVE | 0.5x, and is it up?
You cannot join now: FULL PVE | 0.5x is offline, last seen 12 days 16 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 15 October 2026.
Which Rust version is FULL PVE | 0.5x running?
The server FULL PVE | 0.5x is on Rust network protocol 2634 and build 167398 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does FULL PVE | 0.5x reset?
The record holds too few of FULL PVE | 0.5x's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 18 days 2 hours.
Population
Where does FULL PVE | 0.5x place in the wider field of Rust servers?
Over the last seven days, FULL PVE | 0.5x has #14,419 for player hours, in the top 67% of all ranked servers.
Is FULL PVE | 0.5x a busy server?
The last sighting of FULL PVE | 0.5x was 12 days 16 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on FULL PVE | 0.5x?
The game's browser takes its cue from the tags FULL PVE | 0.5x has set: gmrust (Game mode): Rust survival, played by the standard rules; mp64 (Max players): Its slot count is 64; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): This runs on build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod). 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 lists and filters on Rust Server Score show FULL PVE | 0.5x?
These Rust Server Score lists count FULL PVE | 0.5x among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
Server 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. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
FULL PVE | 0.5x runs which map?
The game generates a procedural map for FULL PVE | 0.5x.
How to join
How should you connect to FULL PVE | 0.5x?
Enter client.connect 45.153.50.47: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 asmp64,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp64
Max playersIts slot count is 64.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
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).