On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,318top 69%
Last wipe191d 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,318 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: 124 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 193 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
The region code for RustServer_13839 is us3, but no region is published. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 160.251.200.240:28015 is the address to use.
How dependable is RustServer_13839, and is it online at the moment?
You can join now: RustServer_13839 is online. The uptime it reports puts the last restart at about 5 days 13 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.
Is RustServer_13839 smooth to play on?
The average over the last 48 hours was 124 server fps, and it never went below 93. Up to 47,138 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 4,580 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is RustServer_13839 running?
Rust network protocol 2623 and build 148916 on Linux is what RustServer_13839 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does RustServer_13839 wipe its map?
There are too few wipes on record for RustServer_13839 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 191 days 15 hours have passed since this world was made.
Player count
Where does RustServer_13839 sit among Rust servers?
Over the last seven days, RustServer_13839 has #15,318 for player hours, in the top 69% of all ranked servers.
Is RustServer_13839 a busy server?
Right now, 0 players are on RustServer_13839, which has 50 slots. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on RustServer_13839?
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; v2623 (Protocol): To get in, your game needs to be on the same version: the protocol is 2623; cs148916 (Build): The game build is 148916; ptrak (Networking): RakNet handles it, the game's default network layer; $rus3 (Region code): us3 is the region code this server uses; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags RustServer_13839 publishes, and the game's server browser reads them. 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_13839 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include RustServer_13839: 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.
Rules and settings
What settings and rules apply on RustServer_13839?
Nothing in the name of RustServer_13839 states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map RustServer_13839 uses?
A procedural map of size 3,000 and seed 15896, generated by the game, is what RustServer_13839 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join RustServer_13839?
To connect, start Rust, press F1, and type client.connect 160.251.200.240:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rus3,v2623,gmrust,cs148916,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.
v2623
ProtocolTo get in, your game needs to be on the same version: the protocol is 2623.
cs148916
BuildThe game build is 148916.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rus3
Region codeus3 is the region code this server uses.
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).