On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,290top 69%
Last wipe22d 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 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,290 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
100/ 100
A+
Runs smoothly: 60 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
30/ 100
F
Lost ground: down 6,020 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in performance (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 69% 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 peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 18 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 7 Oct, 12:32 UTC22d ago
1
–
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
RustServer_847 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 160.251.175.249:28015.
How reliable is RustServer_847, and is it up?
Right now, RustServer_847 is online. According to its reported uptime, the last restart was about 7 days ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does RustServer_847 perform well?
The average over the last 48 hours was 60 server fps, and it never went below 34. At its peak, it held 97,194 entities, including buildings, deployables and all else in the world. Up to 3,495 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is RustServer_847 on?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_847 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does RustServer_847 wipe its map?
The record holds too few of RustServer_847'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. 22 days 10 hours have passed since this world was made.
What happens on RustServer_847 when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 18 hours into the latest wipe.
Population
Where does RustServer_847 place in the wider field of Rust servers?
Over the last seven days, RustServer_847 has #15,290 for player hours, in the top 69% of all ranked servers.
What does the population on RustServer_847 look like?
RustServer_847 is showing 0 players right now, with 50 slots in total. For the last seven days, the average number of players was 0.
Tags and filters
What do RustServer_847's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags RustServer_847 publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show RustServer_847?
Rust Server Score lists that include RustServer_847: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is RustServer_847 set up, and what rules does it keep?
The name of RustServer_847 gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map RustServer_847 uses?
RustServer_847 runs a game-generated procedural map at size 4,000, seed 482920672. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join RustServer_847?
To connect, start Rust, press F1, and type client.connect 160.251.175.249:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 performance (A+); population is the one to work on (F).