RUST METRICSFlight deck · live data
Data live Servers11,634 Players45,438 Populated3,128 Fresh wipes 3 h92 Scan5 min
‹ All servers72.192.52.193:28015
Offline Full Queue Fresh wipe Wipe due No query

The Rusty Beet | Powered by Beets

Offline 72.192.52.193:28015 checked 33d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,670top 71%
Last wipe38d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep27 Sep29 Sep1 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What wipe timing does The Rusty Beet | Powered by Beets follow?

The rhythm of The Rusty Beet | Powered by Beets's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 38 days 5 hours ago the current world was made.

Tags

How should you read the tags on The Rusty Beet | Powered by Beets?

These are the tags The Rusty Beet | Powered by Beets publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does The Rusty Beet | Powered by Beets appear in Rust Metrics lists and filters?

On Rust Metrics, The Rusty Beet | Powered by Beets sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does The Rusty Beet | Powered by Beets sit in the rankings?

Ranking for The Rusty Beet | Powered by Beets: #15,670 on seven-day player hours, top 71% of all ranked servers.

What is the population on The Rusty Beet | Powered by Beets?

Status for The Rusty Beet | Powered by Beets: offline. Last seen 33 days 20 hours ago.

Operator and location

Which location does The Rusty Beet | Powered by Beets run from?

No region comes from The Rusty Beet | Powered by Beets. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 72.192.52.193:28015.

What Rust version is The Rusty Beet | Powered by Beets on?

Reading: The Rusty Beet | Powered by Beets, Rust network protocol 2633 and build 164530, Linux. To get in, your game needs the same protocol; Steam applies the update.

How reliable is The Rusty Beet | Powered by Beets, and is it online now?

The Rusty Beet | Powered by Beets reports offline. The last reading came 33 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 20 September 2026.

Settings and map

What rules does The Rusty Beet | Powered by Beets enforce, and what are its settings?

Check: gather rate. The name The Rusty Beet | Powered by Beets does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is The Rusty Beet | Powered by Beets on?

The game generates a procedural map for The Rusty Beet | Powered by Beets.

Join

How do you connect to The Rusty Beet | Powered by Beets?

Check: join. Open Rust, press F1, then enter client.connect 72.192.52.193:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Game build reading: 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.