Working its way up from the back of the class: #15,483 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
42/ 100
F
Slipped a little: down 2,379 places this week. Nothing a good wipe can't fix.
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.
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
In what location does [PVE] 3x Vanilla-ish | Raidable Bases sit?
You'll find no region listed by [PVE] 3x Vanilla-ish | Raidable Bases. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 176.6.13.174:28015.
How dependable is [PVE] 3x Vanilla-ish | Raidable Bases, and is it online at the moment?
At this moment, [PVE] 3x Vanilla-ish | Raidable Bases is offline; the last time it was seen was 36 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 21 September 2026.
Which Rust version is [PVE] 3x Vanilla-ish | Raidable Bases running?
You will find [PVE] 3x Vanilla-ish | Raidable Bases on Rust network protocol 2633 and build 164530, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does [PVE] 3x Vanilla-ish | Raidable Bases reset?
The record holds too few of [PVE] 3x Vanilla-ish | Raidable Bases's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 37 days 14 hours.
Population
Where does [PVE] 3x Vanilla-ish | Raidable Bases sit among Rust servers?
Over the last seven days, [PVE] 3x Vanilla-ish | Raidable Bases has #15,483 for player hours, in the top 67% of all ranked servers.
How many players does [PVE] 3x Vanilla-ish | Raidable Bases usually have?
It has been 36 days 11 hours since [PVE] 3x Vanilla-ish | Raidable Bases was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on [PVE] 3x Vanilla-ish | Raidable Bases?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags [PVE] 3x Vanilla-ish | Raidable Bases publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [PVE] 3x Vanilla-ish | Raidable Bases appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [PVE] 3x Vanilla-ish | Raidable Bases among them: 3x Rust servers, graded, 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; Gather rate: 3x.
Map and rules
What settings and rules apply on [PVE] 3x Vanilla-ish | Raidable Bases?
[PVE] 3x Vanilla-ish | Raidable Bases sets gather at 3x, as its name suggests. The default of 8 players applies as the group cap. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [PVE] 3x Vanilla-ish | Raidable Bases uses?
[PVE] 3x Vanilla-ish | Raidable Bases runs a procedural map, which the game generates.
How to join
What is the way to join [PVE] 3x Vanilla-ish | Raidable Bases?
Enter client.connect 176.6.13.174: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 asmp50,ptrak,$r?,v2633,^p,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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
ModdedThe game is changed by plugins or settings; you will find it under 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.