Working its way up from the back of the class: #9,559 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
22/ 100
F
Lost ground: down 5,281 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (C−); momentum 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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 44% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
·······
·······
····
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 gap0.9 daysbetween real wipes
wipe-day peak5players, last three wipes
The first 48 hours of its last wipes
Fri 2 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 5, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 08:25 UTC27d ago
5
–
running
2
Thu 1 Oct, 11:44 UTC28d ago
5
–
0.9 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
RustServer_24252 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 160.251.177.100:28015.
How dependable is RustServer_24252, and is it online at the moment?
The server is down: RustServer_24252 is offline now, with the last sighting 16 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is RustServer_24252 on?
The server RustServer_24252 is on Rust network protocol 2634 and build 166586 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does RustServer_24252 wipe, and how often?
The record holds too few of RustServer_24252's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 27 days 9 hours have passed since this world was made.
What happens on RustServer_24252 when wipe day arrives?
Recent wipes have peaked at 5 players on average. 4 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does RustServer_24252 place in the wider field of Rust servers?
Over the last seven days, RustServer_24252 has #9,559 for player hours, in the top 44% of all ranked servers.
What does the population on RustServer_24252 look like?
It has been 16 days 6 hours since RustServer_24252 was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on RustServer_24252?
You'll see RustServer_24252 tagged with 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; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): The game build is 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature RustServer_24252?
These Rust Server Score lists count RustServer_24252 among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on RustServer_24252?
You will find no gather rate in the name of RustServer_24252. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on RustServer_24252?
A procedural map of size 3,000 and seed 23630, generated by the game, is what RustServer_24252 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto RustServer_24252?
To connect, start Rust, press F1, and type client.connect 160.251.177.100: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,cs166586,ts8,^o^z
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.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 standing (C−); momentum is the one to work on (F).