Rust Data

rustdata.spaceservers162.230.243.193:28011.ipynb

Run all rust-data · live

‹ All servers

Online 162.230.243.193:28010 checked 13m ago

Buckeye Beavers

moddedcarbon

Connect

srv = rust.server("162.230.243.193:28011")
print(srv.connect_command)

Right now

srv.summary()
players now 0/60 # 0% full
7-day average 0 # peak –
rank #15,269 # top 69%
last wipe 7d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123403:0012:0022:0007:0016:0001:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608003:0012:0022:0007:0016:0001:00

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 01:26 UTC7d ago 0 NaN 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.

display(srv.map, srv.info())

Map

3000 · seed 152314775
Map of Buckeye Beavers
map
Procedural Map
size
3000
seed
152314775
Open on RustMaps

Server

srv.info()
address
162.230.243.193:28010
region
–
max players
60
group limit
8, the default
wipe schedule
–
last wipe
23 Oct 2026, 01:26 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 151 on average14/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average34/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average4/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average20/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average127/200

Quick answers

From the figures on this page.

Player counts

How does Buckeye Beavers compare in the rankings?

Player hours over seven days put Buckeye Beavers at #15,269, in the top 69% of the ranked set.

How many players does Buckeye Beavers hold at once?

The sample now reads 0 players for Buckeye Beavers, out of 60 slots. Over the last seven days it averaged 0 players.

Server data

How smoothly does Buckeye Beavers run?

Averaged over 48 hours: 58 server fps, never under 55. The entity count peaked at 47,855, covering buildings, deployables and the rest of the world. A high of 3,037 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does Buckeye Beavers run?

Rust network protocol 2635 and build 168909 on Windows is what Buckeye Beavers runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is Buckeye Beavers, and is it up?

Online is the state at the latest refresh for Buckeye Beavers. Count back 5 days 5 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Buckeye Beavers sit?

No region is published by Buckeye Beavers. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 162.230.243.193:28010 is its address.

Rules, settings, map

Which rules apply on Buckeye Beavers, and what settings?

You will not find a gather rate in the string Buckeye Beavers. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. Anti-cheat status: VAC on.

What is the map on Buckeye Beavers?

Buckeye Beavers runs a procedural map of size 3,000 with seed 152314775, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Buckeye Beavers wipe, and on what schedule?

Too few wipes are on record for Buckeye Beavers to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 7 days 1 hours ago, and that is the one in play.

What is wipe day on Buckeye Beavers like?

The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.

Lists and tags

Where does Buckeye Beavers appear among Rust Data lists and filters?

The Rust Data lists that Buckeye Beavers fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on Buckeye Beavers?

The game's server browser reads these tags from Buckeye Beavers: gmrust (Game mode): Rust survival in its standard form; mp60 (Max players): The server lists 60 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to Buckeye Beavers?

In Rust, F1 opens the console: type client.connect 162.230.243.193:28010. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp60,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp60
Max players The server lists 60 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^y
Carbon Runs on Carbon for plugins.

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.

Rust Data 49,072 players 11,686 servers online