On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 50% full
7-day average0peak 1
Rank#11,228top 50%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 5 on average. Plenty of space to grow.
Standingrank on player hours
50/ 100
D
Working its way up from the back of the class: #11,228 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
82/ 100
B+
Mostly smooth: 49 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
26/ 100
F
Lost ground: down 5,303 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 50% 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 peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 14 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 00:26 UTC27d ago
2
–
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 PvE|Prvt|RustServer_4991 based in?
You'll find no region listed by PvE|Prvt|RustServer_4991. Rust Server Score takes the server's word for its location and does not trace the hardware. 133.117.73.235:28015 is the address to use.
How reliable is PvE|Prvt|RustServer_4991, and is it up?
You can join now: PvE|Prvt|RustServer_4991 is online. According to its reported uptime, the last restart was about 5 days 15 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does PvE|Prvt|RustServer_4991 perform well?
It never fell below 36 server fps in the last 48 hours, averaging 49. At its peak, it held 111,948 entities, including buildings, deployables and all else in the world. At its highest, it used 4,338 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does PvE|Prvt|RustServer_4991 sit?
You will find PvE|Prvt|RustServer_4991 on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does PvE|Prvt|RustServer_4991 reset?
The record holds too few of PvE|Prvt|RustServer_4991'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 27 days 14 hours.
What should you expect from wipe day on PvE|Prvt|RustServer_4991?
The average peak on its recent wipes was 2 players. 14 hours after the latest wipe began, the crowd hit its peak.
Population
Where does PvE|Prvt|RustServer_4991 place in the wider field of Rust servers?
In the top 50% of all ranked servers, PvE|Prvt|RustServer_4991 sits at #11,228 for player hours over the last seven days.
How many players does PvE|Prvt|RustServer_4991 usually have?
Right now, 0 players are on PvE|Prvt|RustServer_4991, which has 5 slots. It peaked at 1 and averaged 0 players over the last seven days.
Lists and filters
What do PvE|Prvt|RustServer_4991's tags stand for?
You'll see PvE|Prvt|RustServer_4991 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): Its slot count is 5; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other 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.
Where does PvE|Prvt|RustServer_4991 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include PvE|Prvt|RustServer_4991: Best community servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Server rules
What settings and rules apply on PvE|Prvt|RustServer_4991?
You will find no gather rate in the name of PvE|Prvt|RustServer_4991. The default of 8 players applies as the group cap. It runs pve, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on PvE|Prvt|RustServer_4991?
PvE|Prvt|RustServer_4991 runs a game-generated procedural map at size 4,500, seed 8762. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto PvE|Prvt|RustServer_4991?
Enter client.connect 133.117.73.235: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 asmp5,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max playersIts slot count is 5.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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 uptime (A+); population is the one to work on (F).