On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,335top 69%
Last wipe118d agono schedule published
Next wipe–no wipe 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,335 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: 122 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
49/ 100
D
Slipped a little: down 210 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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
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
RustServer_23462 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 163.44.117.42:28015.
How reliable is RustServer_23462, and is it up?
Right now, RustServer_23462 is online. The uptime it reports puts the last restart at about 17 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does RustServer_23462 perform well?
It never fell below 7 server fps in the last 48 hours, averaging 122. Buildings, deployables and everything else in the world added up to as many as 103,648 entities. At its highest, it used 3,282 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does RustServer_23462 sit?
You will find RustServer_23462 on Rust network protocol 2631 and build 156583, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does RustServer_23462 wipe its map?
RustServer_23462 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 118 days 10 hours.
Player count
Where does RustServer_23462 sit among Rust servers?
Over the last seven days, RustServer_23462 has #15,335 for player hours, in the top 69% of all ranked servers.
What does the population on RustServer_23462 look like?
RustServer_23462 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_23462's tags stand for?
You'll see RustServer_23462 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts16 (Group limit): Teams cap out at 16; v2631 (Protocol): To get in, your game needs to be on the same version: the protocol is 2631; cs156583 (Build): This runs on build 156583; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits 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.
Where does RustServer_23462 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RustServer_23462 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RustServer_23462?
The name of RustServer_23462 gives no gather rate. A group here can reach 16 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on RustServer_23462?
RustServer_23462 runs a game-generated procedural map at size 4,500, seed 486328296. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join RustServer_23462?
Enter client.connect 163.44.117.42: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 asmp50,ptrak,$r?,v2631,gmrust,cs156583,ts16,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts16
Group limitTeams cap out at 16.
v2631
ProtocolTo get in, your game needs to be on the same version: the protocol is 2631.
cs156583
BuildThis runs on build 156583.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).