RUST METRICSFlight deck · live data
Data live Servers11,847 Players98,615 Populated3,861 Fresh wipes 3 h535 Scan5 min
‹ All servers31.23.215.209:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 31.23.215.209:28015 checked 23d 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,648top 65%
Last wipe23d 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
15k10k15k20k4 Oct6 Oct8 Oct9 Oct11 Oct13 Oct

Top 65% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 6 Oct, 08:40 UTC23d 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 LocalRustServer1337 when wipe day comes?

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

When does LocalRustServer1337 wipe?

To tell the rhythm of LocalRustServer1337, 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. 23 days 11 hours ago the current world was made.

Tag meanings

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

These are the tags LocalRustServer1337 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does LocalRustServer1337 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry LocalRustServer1337: 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.

Population

Where does LocalRustServer1337 sit in the rankings?

Ranking for LocalRustServer1337: #14,648 on seven-day player hours, top 65% of all ranked servers.

How full does LocalRustServer1337 get?

LocalRustServer1337 is not responding; status offline, last seen 23 days 11 hours ago.

Server

Where does LocalRustServer1337 sit?

Reading: location. LocalRustServer1337 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 31.23.215.209:28015.

What Rust version is LocalRustServer1337 on?

Rust network protocol 2634 and build 166652 on Windows is the build LocalRustServer1337 runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. LocalRustServer1337 last answered 23 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 4 October 2026.

Rules and settings

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

Reading the name gives no gather rate for LocalRustServer1337. 8 players per group, the default value. The mode is survival. Note the following: 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 off, Valve's system.

Which map is live on LocalRustServer1337?

Procedural map on LocalRustServer1337, made by the game's generator.

How to join

How do you connect to LocalRustServer1337?

To join: start Rust, press F1 and type client.connect 31.23.215.209: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?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build The server runs game build 166652.
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.