RUST METRICSFlight deck · live data
Data live Servers11,718 Players61,678 Populated3,282 Fresh wipes 3 h174 Scan5 min
‹ All servers160.251.212.172:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_7232

Offline 160.251.212.172:28015 checked 9d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,388top 70%
Last wipe21d 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, measured since 20 Sep. 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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 13:27 UTC21d ago 1 – 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 should you expect from wipe day on RustServer_7232?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 3 hours in.

What wipe timing does RustServer_7232 follow?

To tell the rhythm of RustServer_7232, too few of its wipes 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 21 days 10 hours ago.

Tags

How should you read the tags on RustServer_7232?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Build 167231; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from RustServer_7232. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustServer_7232 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustServer_7232: 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 RustServer_7232 sit in the rankings?

Player hours over seven days put RustServer_7232 at #15,388, in the top 70% of all ranked servers.

How full does RustServer_7232 get?

Reading for RustServer_7232: offline at this moment; last seen 9 days 3 hours ago.

Server details

What location is RustServer_7232 hosted in?

No region tag on RustServer_7232. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 160.251.212.172:28015.

What Rust version is RustServer_7232 on?

Version check: Rust network protocol 2634 and build 167231 on Linux, run by RustServer_7232. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on RustServer_7232, and is it online?

Check: connection. RustServer_7232 is offline at this moment. Last contact was 9 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 September 2026.

Map and rules

How is RustServer_7232 configured, and what rules are in force?

No gather rate appears in the name: RustServer_7232. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on RustServer_7232?

From seed 29783, the game generates the procedural map on RustServer_7232. Its size is 3,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto RustServer_7232?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Build 167231.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.