RUST METRICSFlight deck · live data
Data live Servers11,854 Players100,165 Populated3,872 Fresh wipes 3 h533 Scan5 min
‹ All servers176.215.184.231:28015
Online Full Queue Fresh wipe Wipe due No query

Rust Devblog 227

Online 176.215.184.231:28015 checked 11m 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,269top 68%
Last wipe14d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeak
0123421:0006:0015:0001:0010:0019:00

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
15k10k15k20k15 Oct18 Oct21 Oct23 Oct26 Oct29 Oct

Top 68% 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 peak2players, 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 2, 5 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 15:53 UTC14d ago 2 – 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

Wipe schedule

What happens on Rust Devblog 227 when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 5 hours.

What wipe timing does Rust Devblog 227 follow?

To tell the rhythm of Rust Devblog 227, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 14 days 4 hours ago.

Lists and filters

Which tags does Rust Devblog 227 carry, and what do they mean?

Tags published by Rust Devblog 227, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; v2219 (Protocol): Match the game version: protocol 2219 is required; ptrak (Networking): Network layer: RakNet, the standard for the game; h21aa53ea (Custom tag): This tag is non-standard, added by the owner or a plugin; stok (Custom tag): This tag is non-standard, added by the owner or a plugin. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Rust Devblog 227 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust Devblog 227: 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.

Population

Where does Rust Devblog 227 sit in the rankings?

Ranking for Rust Devblog 227: #15,269 on seven-day player hours, top 68% of all ranked servers.

How full does Rust Devblog 227 get?

Current headcount on Rust Devblog 227: 0 players, 100 slots available. A seven-day average of 0 players is the reading.

Server

Where does Rust Devblog 227 sit?

Reading: location. Rust Devblog 227 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 176.215.184.231:28015.

What Rust version is Rust Devblog 227 on?

Reading: Rust Devblog 227, Rust network protocol 2219, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Rust Devblog 227, and is it online?

Check: connection. Rust Devblog 227 is online at this moment. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 15 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does Rust Devblog 227 enforce, and what are its settings?

No gather rate appears in the name: Rust Devblog 227. The group limit is not published. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Rust Devblog 227?

Check: map. Procedural, generated by the game, on Rust Devblog 227.

Connection

How can you get onto Rust Devblog 227?

Check: join. Open Rust, press F1, then enter client.connect 176.215.184.231: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,v2219,h21aa53ea,stok,gmrust

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
v2219
Protocol Match the game version: protocol 2219 is required.
ptrak
Networking Network layer: RakNet, the standard for the game.

Other

h21aa53ea
Custom tag This tag is non-standard, added by the owner or a plugin.
stok
Custom tag This tag is non-standard, added by the owner or a plugin.

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.