Working its way up from the back of the class: #15,519 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
19/ 100
F
Lost ground: down 9,490 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 8 Oct. 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 peak4players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 18 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 04:02 UTC20d ago
4
–
running
0
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
Which region is SOC Raidable Bases Mod PVE based in?
No region is published for SOC Raidable Bases Mod PVE. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 157.85.91.32:21853.
Is SOC Raidable Bases Mod PVE up, and how steady is its uptime?
You cannot join now: SOC Raidable Bases Mod PVE is offline, last seen 16 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 8 October 2026, Rust Server Score saw it for the first time.
On what Rust version does SOC Raidable Bases Mod PVE sit?
Rust network protocol 2634 and build 167398 on Linux is what SOC Raidable Bases Mod PVE runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does SOC Raidable Bases Mod PVE wipe its map?
The record holds too few of SOC Raidable Bases Mod PVE'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 20 days 15 hours.
What happens on SOC Raidable Bases Mod PVE when wipe day arrives?
The average peak on its recent wipes was 4 players. Peak numbers came 18 hours into the latest wipe.
Player numbers
What position does SOC Raidable Bases Mod PVE hold in the rankings?
In the top 71% of all ranked servers, SOC Raidable Bases Mod PVE sits at #15,519 for player hours over the last seven days.
What does the population on SOC Raidable Bases Mod PVE look like?
It has been 16 days 5 hours since SOC Raidable Bases Mod PVE was last seen, and it is offline right now.
Tags and filters
How should you read the tags on SOC Raidable Bases Mod PVE?
gmrust (Game mode): Rust survival, played by the standard rules; mp75 (Max players): Its slot count is 75; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): The game build is 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^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 SOC Raidable Bases Mod PVE publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show SOC Raidable Bases Mod PVE?
These Rust Server Score lists count SOC Raidable Bases Mod PVE among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on SOC Raidable Bases Mod PVE?
The name of SOC Raidable Bases Mod PVE gives no gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
SOC Raidable Bases Mod PVE runs which map?
The game generates the procedural map on SOC Raidable Bases Mod PVE at size 4,500 with seed 50000. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Getting in
How do you get onto SOC Raidable Bases Mod PVE?
To connect, start Rust, press F1, and type client.connect 157.85.91.32:21853. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp75,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp75
Max playersIts slot count is 75.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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. Strongest in standing (F); momentum is the one to work on (F).