Working its way up from the back of the class: #16,728 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
45/ 100
D
Slipped a little: down 1,667 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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 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 70% of all ranked servers. Ranked on player hours over the last seven days.
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
You'll find no region listed by RustServer_3991. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 160.251.170.78:28015 is the address to use.
How reliable is RustServer_3991, and is it up?
You cannot join now: RustServer_3991 is offline, last seen 28 days 1 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does RustServer_3991 sit?
You will find RustServer_3991 on Rust network protocol 2633 and build 165217, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does RustServer_3991 wipe, and how often?
There are too few wipes on record for RustServer_3991 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 53 days 3 hours.
Population
Where does RustServer_3991 place in the wider field of Rust servers?
In the top 70% of all ranked servers, RustServer_3991 sits at #16,728 for player hours over the last seven days.
What does the population on RustServer_3991 look like?
RustServer_3991 is offline at the moment; the last time it was seen was 28 days 1 hours ago.
Tags
How should you read the tags on RustServer_3991?
The game's browser takes its cue from the tags RustServer_3991 has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. 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.
Where does RustServer_3991 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RustServer_3991 among them: 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.
Map and rules
Which rules does RustServer_3991 enforce, and what are its settings?
You will find no gather rate in the name of RustServer_3991. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RustServer_3991 uses?
The game generates the procedural map on RustServer_3991 at size 3,500 with seed 1746005783. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join RustServer_3991?
To connect, start Rust, press F1, and type client.connect 160.251.170.78: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,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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 momentum (D); standing is the one to work on (F).