Working its way up from the back of the class: #15,400 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 170 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); wipes are 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 19 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
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
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.
usual gap18.4 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 12 OctThu 24 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 14 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 20:32 UTC16d ago
1
–
running
0
Thu 24 Sep, 10:00 UTC35d ago
2
halved by day 1
18.4 days
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
No region is published for RustServer_4158. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 160.251.235.82:28015.
Is RustServer_4158 up, and how steady is its uptime?
The server is down: RustServer_4158 is offline now, with the last sighting 8 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 19 September 2026, Rust Server Score saw it for the first time.
Which Rust version is RustServer_4158 running?
The server RustServer_4158 is on Rust network protocol 2634 and build 167584 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does RustServer_4158 reset?
RustServer_4158 has not had enough wipes recorded to reveal its 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 16 days 20 hours.
What happens on RustServer_4158 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 14 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
Where does RustServer_4158 sit among Rust servers?
In the top 69% of all ranked servers, RustServer_4158 sits at #15,400 for player hours over the last seven days.
Is RustServer_4158 a busy server?
It has been 8 days 19 hours since RustServer_4158 was last seen, and it is offline right now.
Tags
What do RustServer_4158's tags stand for?
The game's browser takes its cue from the tags RustServer_4158 has set: 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; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167584 (Build): This runs on build 167584; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. 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 RustServer_4158 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RustServer_4158 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RustServer_4158?
The name of RustServer_4158 gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map RustServer_4158 uses?
The game generates the procedural map on RustServer_4158 at size 3,000 with seed 22703. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to RustServer_4158?
To connect, start Rust, press F1, and type client.connect 160.251.235.82:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs167584,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.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167584
BuildThis runs on build 167584.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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.
A term to build on. Strongest in momentum (D); wipes are the one to work on (F).