RUST METRICSFlight deck · live data
Data live Servers11,652 Players47,233 Populated3,140 Fresh wipes 3 h114 Scan5 min
‹ All servers133.32.227.229:28015
Offline Full Queue Fresh wipe Wipe due No query

WHA_RUST_Server

Offline 133.32.227.229:28015 checked 38d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#14,489no region published
Last wipe38d 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
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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

01234+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
Sun 20 Sep, 07:16 UTC39d ago 1 – running 1

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

Reset cycle

What happens on WHA_RUST_Server when wipe day comes?

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

When does WHA_RUST_Server wipe?

To tell the rhythm of WHA_RUST_Server, 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 in play was created 38 days 22 hours ago.

Tags

How should you read the tags on WHA_RUST_Server?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from WHA_RUST_Server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show WHA_RUST_Server?

On Rust Metrics, WHA_RUST_Server sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does WHA_RUST_Server hold among Rust servers?

Ranking for WHA_RUST_Server: #14,489 on seven-day player hours, top – of all ranked servers.

How full does WHA_RUST_Server get?

Reading for WHA_RUST_Server: offline at this moment; last seen 38 days 22 hours ago.

Server

What location is WHA_RUST_Server hosted in?

Reading: location. WHA_RUST_Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 133.32.227.229:28015.

What Rust version is WHA_RUST_Server on?

Version check: Rust network protocol 2633 and build 164530 on Windows, run by WHA_RUST_Server. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. WHA_RUST_Server is offline at this moment. Last contact was 38 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on WHA_RUST_Server?

Check: gather rate. The name WHA_RUST_Server does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on WHA_RUST_Server?

The game generates a procedural map for WHA_RUST_Server.

Connection

How can you get onto WHA_RUST_Server?

To join: start Rust, press F1 and type client.connect 133.32.227.229:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build The server runs game build 164530.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.