On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now0/ ?
7-day average0peak –
Rank#15,348top 69%
Last wipe24d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,348 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
66/ 100
C+
Slows down under load at times: 40 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 175 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in uptime (A+); 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
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 20 Oct. 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
In what location does Hat's Plugin Development sit?
No region is published for Hat's Plugin Development. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 166.1.120.60:28039.
Is Hat's Plugin Development up, and how steady is its uptime?
The server is up: Hat's Plugin Development is online now. The uptime it reports puts the last restart at about 45 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. It was first seen by Rust Server Score on 20 October 2026.
Does Hat's Plugin Development perform well?
It never fell below 35 server fps in the last 48 hours, averaging 40. Buildings, deployables and everything else in the world added up to as many as 4,277 entities. Up to 785 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does Hat's Plugin Development sit?
Rust network protocol 2635 and build 168909 on Linux is what Hat's Plugin Development runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does Hat's Plugin Development wipe, and how often?
There are too few wipes on record for Hat's Plugin Development to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 24 days 1 hours have passed since this world was made.
Player numbers
Where does Hat's Plugin Development sit among Rust servers?
Over the last seven days, Hat's Plugin Development has #15,348 for player hours, in the top 69% of all ranked servers.
Is Hat's Plugin Development a busy server?
Hat's Plugin Development has 0 players at the moment. Over the past seven days, the average player count was 0.
Tags and filters
How should you read the tags on Hat's Plugin Development?
gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): 0 slots are available; ts50 (Group limit): A team can hold 50 players at most; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Hat's Plugin Development publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Hat's Plugin Development?
These Rust Server Score lists count Hat's Plugin Development among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is Hat's Plugin Development set up, and what rules does it keep?
The name of Hat's Plugin Development gives no gather rate. A group here can reach 50 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on Hat's Plugin Development?
A procedural map of size 1,000 and seed 1, generated by the game, is what Hat's Plugin Development runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto Hat's Plugin Development?
Enter client.connect 166.1.120.60:28039 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 asmp0,ptrak,$r?,v2635,gmrust,cs168909,ts50,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max players0 slots are available.
ts50
Group limitA team can hold 50 players at most.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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 uptime (A+); standing is the one to work on (F).