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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
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
No region is published for Server PVE Survivor. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 94.181.174.133:28015.
How reliable is Server PVE Survivor, and is it up?
The server is down: Server PVE Survivor is offline now, with the last sighting 43 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 15 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Server PVE Survivor running?
Rust network protocol 2633 and build 163493 on Windows is what Server PVE Survivor runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Server PVE Survivor wipe its map?
Server PVE Survivor has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 47 days 21 hours.
Player count
Where does Server PVE Survivor sit among Rust servers?
Over the last seven days, Server PVE Survivor has #13,258 for player hours, in the top – of all ranked servers.
How many players does Server PVE Survivor usually have?
It has been 43 days 16 hours since Server PVE Survivor was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Server PVE Survivor?
You'll see Server PVE Survivor tagged with gmrust (Game mode): Survival in the standard Rust style; mp15 (Max players): The server holds 15 slots; 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; cs163493 (Build): The game build is 163493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^p (PvE): Players do not fight one another here; the world is the danger; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon 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.
Which Rust Server Score filters and lists feature Server PVE Survivor?
These Rust Server Score lists count Server PVE Survivor among them: 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 Carbon ^y; Group limit: 5 or more.
Map and rules
What settings and rules apply on Server PVE Survivor?
You will find no gather rate in the name of Server PVE Survivor. 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 Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Server PVE Survivor?
The game generates a procedural map for Server PVE Survivor.
How to join
What is the way to join Server PVE Survivor?
To connect, start Rust, press F1, and type client.connect 94.181.174.133:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp15,ptrak,$r?,v2633,^z,^y,^p,gmrust,cs163493,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp15
Max playersThe server holds 15 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163493
BuildThe game build is 163493.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon 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.
Not enough figures yet to write a report. Check back after a few days on the list.