RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers95.27.147.22:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1567

Offline 95.27.147.22:28015 checked 19d 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,506top 66%
Last wipe24d 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 Sep24 Sep4 Oct8 Oct12 Oct16 Oct

Top 66% 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 06:32 UTC24d 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 should you expect from wipe day on LocalRustServer1567?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does LocalRustServer1567 follow?

The rhythm of LocalRustServer1567'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 in play was created 24 days 13 hours ago.

Tags

How should you read the tags on LocalRustServer1567?

These are the tags LocalRustServer1567 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Build 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LocalRustServer1567 appear in Rust Metrics lists and filters?

On Rust Metrics, LocalRustServer1567 sits in these lists: 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.

Player count

Where does LocalRustServer1567 sit in the rankings?

Ranking for LocalRustServer1567: #14,506 on seven-day player hours, top 66% of all ranked servers.

What player count does LocalRustServer1567 carry?

LocalRustServer1567 is not responding; status offline, last seen 19 days 16 hours ago.

Server

Where does LocalRustServer1567 sit?

No region comes from LocalRustServer1567. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 95.27.147.22:28015.

What Rust version is LocalRustServer1567 on?

Reading: LocalRustServer1567, Rust network protocol 2634 and build 167231, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is LocalRustServer1567 up, and how often does it stay up?

Reading: offline. LocalRustServer1567 last answered 19 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 September 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for LocalRustServer1567. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is off. That is Valve's anti-cheat.

What map is LocalRustServer1567 on?

Check: map. Procedural, generated by the game, on LocalRustServer1567.

Connection

How can you get onto LocalRustServer1567?

Press F1 in Rust and enter client.connect 95.27.147.22:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Build 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.