RUST METRICSFlight deck · live data
Data live Servers11,726 Players49,195 Populated3,240 Fresh wipes 3 h114 Scan5 min
‹ All servers13.140.146.239:28015
Offline Full Queue Fresh wipe Wipe due No query

BEANS2

Offline 13.140.146.239:28015 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 75 150 225 300 PAX 0 /300

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,349top 69%
Last wipe6d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

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

PLAN

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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 20:52 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.

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 timing

What happens on BEANS2 when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does BEANS2 wipe?

The rhythm of BEANS2'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. The world it runs now was made 6 days 3 hours ago.

Lists and filters

Which tags does BEANS2 carry, and what do they mean?

These are the tags BEANS2 publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp300 (Max players): The server holds 300 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $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 BEANS2 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring BEANS2: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

What position does BEANS2 hold among Rust servers?

Player hours over seven days put BEANS2 at #15,349, in the top 69% of all ranked servers.

What is the population on BEANS2?

Reading for BEANS2: offline at this moment; last seen 6 days 3 hours ago. A seven-day average of 0 players is the reading.

Operator and location

Which location does BEANS2 run from?

No region comes from BEANS2. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 13.140.146.239:28015.

What Rust version is BEANS2 on?

Rust network protocol 2635 and build 168909 on Linux is the build BEANS2 runs. Matching protocol is required to join. Let Steam update your game.

How reliable is BEANS2, and is it online now?

Check: connection. BEANS2 is offline at this moment. Last contact was 6 days 3 hours ago. Uptime for the last 6 full days: 0 of 144 hours, or 0%. Check: first contact. Rust Metrics logged it on 22 October 2026.

Rules and settings

What rules does BEANS2 enforce, and what are its settings?

No gather rate appears in the name: BEANS2. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is BEANS2 on?

The game generates a procedural map for BEANS2.

Join

How do you connect to BEANS2?

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

PLACARDS

Server tags

what each one means

Published as mp300,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp300
Max players The server holds 300 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.