On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 600% full
7-day average0peak –
Rank#15,276top 69%
Last wipe6d agono schedule published
Next wipe–too few wipes 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 60 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,276 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
96/ 100
A+
Runs smoothly: 58 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
50/ 100
D
Holding steady: down 151 places this week.
A fair term, with more to come.
Strongest in uptime (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
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····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.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 01:26 UTC6d ago
0
–
running
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
You'll find no region listed by Buckeye Beavers. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 162.230.243.193:28010.
How reliable is Buckeye Beavers, and is it up?
Right now, Buckeye Beavers is online. The uptime it reports puts the last restart at about 5 days 1 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
How well does Buckeye Beavers run?
It averaged 58 server fps over the last 48 hours, with a low of 55. Buildings, deployables and everything else in the world added up to as many as 47,645 entities. At its highest, it used 3,037 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is Buckeye Beavers on?
Rust network protocol 2635 and build 168909 on Windows is what Buckeye Beavers runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Buckeye Beavers reset?
Buckeye Beavers has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 6 days 21 hours.
What should you expect from wipe day on Buckeye Beavers?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Population
What position does Buckeye Beavers hold in the rankings?
In the top 69% of all ranked servers, Buckeye Beavers sits at #15,276 for player hours over the last seven days.
Is Buckeye Beavers a busy server?
With 60 slots available, Buckeye Beavers currently has 0 players. For the last seven days, the average number of players was 0.
Tags
How should you read the tags on Buckeye Beavers?
gmrust (Game mode): Rust survival, played by the standard rules; mp60 (Max players): The server holds 60 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon are the tags Buckeye Beavers 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.
Where does Buckeye Beavers appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Buckeye Beavers among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Server rules
What settings and rules apply on Buckeye Beavers?
Nothing in the name of Buckeye Beavers states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Buckeye Beavers uses?
Buckeye Beavers runs a game-generated procedural map at size 3,000, seed 152314775. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join Buckeye Beavers?
Enter client.connect 162.230.243.193:28010 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 asmp60,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp60
Max playersThe server holds 60 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
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+); population is the one to work on (F).