Not ranked yet, so there is no place in the school to report.
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
49/ 100
D
Slipped a little: down 187 places this week. Nothing a good wipe can't fix.
A term to build on.
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
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?
[PVE] 3x Vanilla-ish | Raidable Bases leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 176.6.76.241:28015 is the address to use.
How reliable is [PVE] 3x Vanilla-ish | Raidable Bases, and is it up?
At this moment, [PVE] 3x Vanilla-ish | Raidable Bases is offline; the last time it was seen was 37 days 4 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 20 September 2026.
Which Rust version is [PVE] 3x Vanilla-ish | Raidable Bases running?
Rust network protocol 2633 and build 164530 on Linux is what [PVE] 3x Vanilla-ish | Raidable Bases runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does [PVE] 3x Vanilla-ish | Raidable Bases wipe, and how often?
[PVE] 3x Vanilla-ish | Raidable Bases 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 37 days 4 hours.
Population
What position does [PVE] 3x Vanilla-ish | Raidable Bases hold in the rankings?
Over the last seven days, [PVE] 3x Vanilla-ish | Raidable Bases has #14,707 for player hours, in the top – of all ranked servers.
What does the population on [PVE] 3x Vanilla-ish | Raidable Bases look like?
It has been 37 days 4 hours since [PVE] 3x Vanilla-ish | Raidable Bases was last seen, and it is offline right now.
Tags
How should you read the tags on [PVE] 3x Vanilla-ish | Raidable Bases?
The game's browser takes its cue from the tags [PVE] 3x Vanilla-ish | Raidable Bases has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^p (PvE): Players do not fight one another here; the world is the danger; ^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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show [PVE] 3x Vanilla-ish | Raidable Bases?
Rust Server Score lists that include [PVE] 3x Vanilla-ish | Raidable Bases: 3x Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: 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
Which rules does [PVE] 3x Vanilla-ish | Raidable Bases enforce, and what are its settings?
[PVE] 3x Vanilla-ish | Raidable Bases sets gather at 3x, as its name suggests. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. 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?
The game generates a procedural map for [PVE] 3x Vanilla-ish | Raidable Bases.
How to join
How should you connect to [PVE] 3x Vanilla-ish | Raidable Bases?
To connect, start Rust, press F1, and type client.connect 176.6.76.241:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^p,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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.